Method and device for transmitting and receiving signals in wireless communication system

ABSTRACT

A method and device for transmitting and receiving signals in a wireless communication system according to one embodiment of the present invention perform a 2-step or 4-step random access process in a shared spectrum. For the transmission of a PUSCH corresponding to an RAR in the 4-step random access process or a fallback-RAR in the 2-step random access process, the channel access type for the PUSCH is determined on the basis of a specific field of an RAR grant in the RAR.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of Internation Application No.PCT/KR2020/013376, filed on Sep. 29, 2020, which claims the benefit ofearlier filing date and right of priority to Korean Application No.10-2019-0123313, filed on Oct. 4, 2019, Korean Application No.10-2019-0142875, filed on Nov. 8, 2019, and Korean Application No.10-2019-0160927, filed on Dec. 5, 2019. The disclosures of the priorapplications are incorporated by reference in their entirety.

TECHNICAL FIELD

The present disclosure relates to a method and an apparatus used in awireless communication system.

BACKGROUND

Wireless communication systems are being widely deployed to providevarious types of communication services such as voice and data. Ingeneral, a wireless communication system is multiple access system thatcan support communication with multiple users by sharing availablesystem resources (e.g., bandwidth, transmission power and the like).Examples of the multiple access system include CDMA (Code DivisionMultiple Access) system, FDMA (Frequency Division Multiple Access)system, TDMA (Time Division Multiple Access) system, OFDMA (OrthogonalFrequency Division Multiple Access) system, and SC-FDMA (Single CarrierFrequency Division Multiple Access) system and the like.

SUMMARY

An technical problem of the present disclosure is to provide a methodfor receiving and transmitting a signal for efficiently performing arandom access procedure in a wireless communication system and anapparatus therefor.

The technical problem of the present disclosure is not limited to theabove-described technical problem, and other technical problems may beinferred from the embodiments of the present disclosure.

The present disclosure is to provide a method and an apparatus forreceiving and transmitting a signal in a wireless communication system.

As an aspect of the present disclosure, a method for transmitting andreceiving a signal by a User Equipment (UE) operating in a wirelesscommunication system includes receiving Random Access Response (RAR)based on a Physical Random Access Channel), and transmitting a PhysicalUplink Shared Channel (PUSCH) based on the RAR, and a channel accesstype for the PUSCH in shared spectrum channel access is determined basedon a specific field of a RAR grant in the RAR.

As another aspect of the present disclosure, a communication device(auser equipment (UE)) for transmitting and receiving a signal in awireless communication system includes at least one transceiver; atleast one processor; and at least one memory operatively coupled to theat least one processor and storing instructions that, based on beingexecuted, cause the at least one processor to perform a specificoperation, and the specific operation includes: receiving random accessresponse (RAR) based on a physical random access channel (PRACH); andtransmitting a physical uplink shared channel (PUSCH) based on the RAR,and a channel access type for the PUSCH in shared spectrum channelaccess is determined based on a specific field of a RAR grant in theRAR.

As another aspect of the present disclosure, a communication device fora user equipment (UE) includes at least one processor; and at least onecomputer memory operatively coupled to the at least one processor andbased on being executed, causing the at least one processor to performan operation, and the operation includes: receiving Random AccessResponse (RAR) based on a Physical Random Access Channel), andtransmitting a Physical Uplink Shared Channel (PUSCH) based on the RAR,and a channel access type for the PUSCH in shared spectrum channelaccess is determined based on a specific field of a RAR grant in theRAR.

As another aspect of the present disclosure, a computer-readable storagemedium comprising at least one computer program for causing at least oneprocessor to perform an operation is provided and the operationcomprises receiving Random Access Response (RAR) based on a PhysicalRandom Access Channel), and transmitting a Physical Uplink SharedChannel (PUSCH) based on the RAR, and a channel access type for thePUSCH in shared spectrum channel access is determined based on aspecific field of a RAR grant in the RAR.

As another aspect of the present disclosure, a method of transmittingand receiving a signal by a base station in a wireless communicationsystem comprises transmitting a random access response (RAR) based on aphysical random access channel (PRACH); and receiving a physical uplinkshared channel (PUSCH) based on the RAR, and a channel access type forthe PUSCH in shared spectrum channel access is determined based on aspecific field of a RAR grant in the RAR.

As another aspect of the present disclosure, a communication device(abase station) for transmitting and receiving a signal in a wirelesscommunication system comprises at least one transceiver; at least oneprocessor; and at least one memory operatively coupled to the at leastone processor and storing instructions that, based on being executed,cause the at least one processor to perform a specific operation, andthe specific operation includes: transmitting a random access response(RAR) based on a physical random access channel (PRACH); and receiving aphysical uplink shared channel (PUSCH) based on the RAR and a channelaccess type for the PUSCH in shared spectrum channel access isdetermined based on a specific field of a RAR grant in the RAR.

In the methods and apparatuses, the specific field is used as a PUSCHfrequency resource allocation field for a non-shared spectrum.

In the methods and apparatuses, among 14 bits for the PUSCH frequencyresource allocation field for the non-shared spectrum, 2 bits are usedfor the specific field for a shared spectrum.

In the methods and apparatuses, among the 14 bits, 12 bits except forthe 2 bits are used for the PUSCH frequency resource allocation fieldfor a shared spectrum.

In the methods and apparatuses, the 12 bits of the PUSCH frequencyresource allocation field is interpreted by inserting 2 bits of MostSignificant Bits (MSBs) having a value of 0 to the 12 bits.

The communication devices may include at least a terminal, a network,and an autonomous vehicle capable of communicating with an autonomousvehicle other than the communication device.

The above-described aspects of the present disclosure are only some ofthe preferred embodiments of the present disclosure, and variousembodiments in which the technical features of the present disclosureare reflected may be derived and understood by those of ordinary skillin the art based on the detailed description of the present disclsoureto be described below.

According to one embodiment of the present disclosure, when the randomaccess procedure between a UE and a base station is performed, there isan advantage that a more efficient random access procedure may beperformed through an operation differentiated from the conventionaldisclosure.

The technical effects of the present disclosure is not limited to theabove-described technical effects, and other technical effects may beinferred from the embodiments of the present disclosure.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 illustrates a structure of a radio frame.

FIG. 2 illustrates a resource grid of a slot.

FIG. 3 illustrates an example in which a physical channel is mapped in aslot.

FIG. 4 illustrates an ACK/NACK transmission process.

FIGS. 5A and 5B illustrate a wireless communication system supporting anunlicensed band.

FIG. 6 illustrates a method of occupying resource within an unlicensedband.

FIGS. 7 and 8 are CAP (Channel Access Procedure) flow charts for signaltransmission through the unlicensed band.

FIG. 9 illustrates an RB interlace.

FIGS. 10A to 11B are diagrams related to a random access procedure.

FIGS. 12 to 17 are diagrams for describing a random access procedureaccording to an embodiment of the present disclosure.

FIGS. 18 to 21 illustrate apparatuses according to an embodiment of thepresent disclosure.

DETAILED DESCRIPTION

The following techniques may be used in various radio access systemssuch as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, and the like. CDMA may beimplemented with a radio technology such as Universal Terrestrial RadioAccess (UTRA) or CDMA2000. TDMA may be implemented with a radiotechnology such as Global System for Mobile communications (GSM)/GeneralPacket Radio Service (GPRS)/Enhanced Data Rates for GSM Evolution(EDGE). OFDMA may be implemented with a radio technology such as IEEE802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA),and the like. UTRA is part of the Universal Mobile TelecommunicationsSystem (UMTS). 3GPP (3rd Generation Partnership Project) Long TermEvolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA andLTE-A (Advanced)/LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR(New Radio or New Radio Access Technology) is an evolved version of 3GPPLTE/LTE-A/LTE-A pro.

For clarity of description, it is described based on a 3GPPcommunication system (e.g., LTE, NR), but the technical idea of thepresent disclosure is not limited thereto. LTE refers to technologyafter 3GPP TS 36.xxx Release 8. In detail, LTE technology after 3GPP TS36.xxx Release 10 is referred to as LTE-A, and LTE technology after 3GPPTS 36.xxx Release 13 is referred to as LTE-A pro. 3GPP NR refers totechnology after TS 38.xxx Release 15. LTE/NR may be referred to as a3GPP system. “xxx” stands for standard document detail number. LTE/NRmay be collectively referred to as a 3GPP system. For background art,terms, abbreviations, etc. used in the description of the presentdisclosure, reference may be made to matters described in standarddocuments published before the present disclosure. For example, it mayrefer to the following documents:

3GPP NR

-   -   38.211: Physical channels and modulation    -   38.212: Multiplexing and channel coding    -   38.213: Physical layer procedures for control    -   38.214: Physical layer procedures for data    -   38.300: NR and NG-RAN Overall Description    -   38.331: Radio Resource Control (RRC) protocol specification

FIG. 1 illustrates the structure of a radio frame used in NR.

Uplink (UL) and downlink (DL) transmission in NR consists of frames. Aradio frame has a length of 10 ms and is defined as two 5 ms half-frames(Half-Frame, HF). A half-frame is defined as 5 lms subframes (Subframe,SF). A subframe is divided into one or more slots, and the number ofslots in a subframe depends on subcarrier spacing (SCS). Each slotincludes 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP).When a normal CP (CP) is used, each slot includes 14 symbols. When anextended CP (extended CP) is used, each slot includes 12 symbols. Here,the symbol may include an OFDM symbol (or, a CP-OFDM symbol) and anSC-FDMA symbol (or, a DFT-s-OFDM symbol).

Table 1 exemplifies that the number of symbols per a slot, the number ofslots per a frame, and the number of slots per a subframe vary accordingto the SCS when the normal CP is used.

TABLE 1 SCS (15*2{circumflex over ( )}u) Nslotsymb Nframe, uslotNsubframe, uslot 15 kHz (u = 0) 14 10 1 30 kHz (u = 1) 14 20 2 60 kHz (u= 2) 14 40 4 120 kHz (u = 3) 14 80 8 240 kHz (u = 4) 14 160 16 *Nslotsymb: The number of symbols in a slot * Nframe, uslot: The numberof slots in a frame * Nsubframe, uslot: The number of slots in asubframe

Table 2 exemplifies that the number of symbols per a slot, the number ofslots per a frame, and the number of slots per a subframe vary accordingto the SCS when the extended CP is used.

TABLE 2 SCS (15*2{circumflex over ( )}u) Nslotsymb Nframe, uslotNsubframe, uslot 60 kHz (u = 2) 12 40 4

In the NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) may beconfigured differently between a plurality of cells merged into one userequipment (UE). Accordingly, an (absolute time) duration of a timeresource (e.g., SF, slot, or TTI) (commonly referred to as TU (TimeUnit) for convenience) composed of the same number of symbols may beconfigured differently between the merged cells.

NR supports multiple OFDM(Orthogonal Frequency Division Multiplexing)numerology (e.g., subcarrier spacing, SCS) to support various 5Gservices. For example, when the SCS is 15 kHz, it supports a wide areain traditional cellular bands, and when the SCS is 30 kHz/60 kHz, itsupports dense-urban, lower latency and a wider carrier bandwidth.

NR frequency band is defined as two types of frequency range (FR)(FR1,FR2). FR1/FR2 may be configured as shown in Table 3 below. In addition,FR2 may mean a millimeter wave (mmW).

TABLE 3 Frequency Range Corresponding frequency designation rangeSubcarrier Spacing FR1  450 MHz-7125 MHz  15, 30, 60 kHz FR2 24250MHz-52600 MHz 60, 120, 240 kHz

FIG. 2 exemplifies a slot structure of an NR frame.

A slot includes a pluarlity of symbols in a time domain. For example, inthe case of a normal CP, one slot includes 14 symbols, and in the caseof an extended CP, one slot includes 12 symbols. The carrier includes aplurality of subcarriers in a frequency domain. A resource block (RB) isdefined as a plurality of (e.g., 12) consecutive subcarriers in afrequency domain. A plurality of RB interlaces (simply, interlaces) maybe defined in a frequency domain. Interlace m∈{0, 1, . . . , M−1} may becomposed of (common) RB {m, M+m, 2M+m, 3M+m, . . . }. M represents thenumber of interlaces. BWP (Bandwidth Part) is defined as a plurality ofconsecutive RBs (e.g., physical RB, PRB) in the frequency domain, andmay correspond to one OFDM numerology (e.g., SCS(u), CP length, etc.). Acarrier may include a maximum of N (e.g., 5) BWPs. Data communication isperformed through the activated BWP, and only one BWP can be activatedfor one UE in one cell/carrier. Each element in the resource grid isreferred to as a resource element (RE), and one modulation symbol may bemapped.

In a wireless communication system, the UE receives information throughdownlink (DL) from the base station and the UE transmits informationthrough uplink (UL) to the base station. Information transmitted andreceived between the base station and the UE includes data and variouscontrol information, and various physical channels/signals existaccording to the type/use of the information they transmit and receive.A physical channel corresponds to a set of resource elements (REs)carrying information derived from a higher layer. A physical signalcorresponds to a set of resource elements (RE) used by the physicallayer (PHY), but does not carry information derived from a higher layer.The higher layer includes a Medium Access Control (MAC) layer, a RadioLink Control (RLC) layer, a Packet Data Convergence Protocol (PDCP)layer, a Radio Resource Control (RRC) layer, and the like.

DL physical channel includes PBCH (Physical Broadcast Channel), PDSCH(Physical Downlink Shared Channel) and PDCCH (Physical Downlink ControlChannel). DL physical signal includes DL RS (Reference Signal), PSS(Primary synchronization signal) and SSS (Secondary synchronizationsignal). DL reference signal (RS) includes DM-RS (Demodulation RS),PT-RS (Phase-tracking RS) and CSI-RS (Channel-state information RS). ULphysical channel includes PRACH(Physical Random Access Channel), PUSCH(Physical Uplink Shared Channel) and PUCCH (Physical Uplink ControlChannel). UL physical signal includes UL RS. UL RS includes DM-RS, PT-RSand SRS (Sounding RS).

FIG. 3 illustrates an example in which a physical channel is mapped in aslot.

A DL control channel, DL or UL data, UL control channel, etc. may all beincluded in one slot. For example, the first N symbols in a slot may beused to transmit a DL control channel (hereinafter, DL control region),and the last M symbols in a slot may be used to transmit a UL controlchannel (hereinafter, UL control region). N and M are each an integergreater than or equal to 0. A resource region (hereinafter, referred toas a data region) between the DL control region and the UL controlregion may be used for DL data transmission or for UL data transmission.A time gap for DL-to-UL or UL-to-DL switching may exist between thecontrol region and the data region. The PDCCH may be transmitted in theDL control region, and the PDSCH may be transmitted in the DL dataregion. Some symbols at the time of switching from DL to UL in a slotmay be used as a time gap.

In this present disclosure, the base station may be, for example,gNodeB.

Downlink (DL) Physical Channel/Signal

(1) PDSCH

PDSCH carries a DL-shared transport block (DL-SCH TB). TB is coded asCodeWord (CW) and then transmitted through a scrambling and modulationprocedures. CW includes one or more code blocks (CBs). The one or moreCBs are grouped into one CBG (CB group). According to configuration ofthe cell, PDSCH carry can carry up to two CWs. Scrambling and modulationare performed for each CW, and modulation symbols generated from each CWare mapped to one or more layers. Each layer is mapped to a resourcetogether with DMRS through precoding, and transmitted through acorresponding antenna port. The PDSCH may be dynamically scheduled bythe PDCCH or semi-statically (configured scheduling, CS) based on higherlayer (e.g., RRC) signaling (and/or Layer 1 (L1) signaling (e.g.,PDCCH)). Accordingly, in dynamic scheduling, PDSCH transmission isaccompanied by a PDCCH, but in CS, PDSCH transmission is not accompaniedby a PDCCH. CS includes semi-persistent scheduling (SPS).

(2) PDCCH

PDCCH carries DCI (Downlink Control Information). For example, PDCCHcarries DL-SCH transmission format and resource allocation,frequency/time resource allocation information for UL-SCH (sharedchannel), paging information on PCH (paging channel), system informationon DL-SCH, random access response transmitted on PDSCH Frequency/timeresource allocation information for higher layer control messages suchas (RAR), transmit power control commands, and information onactivation/deactivation of SPS/CS (Configured Scheduling). Various DCIformats are provided according to information in the DCI.

Table 4 illustrates DCI formats transmitted through the PDCCH.

TABLE 4 DCI format Usage 0_0 Scheduling of PUSCH in one cell 0_1Scheduling of one or multiple PUSCH in one cell, or indicating downlinkfeedback information for configured grant PUSCH (CG-DFI) 1_0 Schedulingof PDSCH in one cell 1_1 Scheduling of PDSCH in one cell, and/ortriggering one shot HARQ-ACK codebook feedback 2_0 Notifying a group ofUEs of the slot format, available RB sets, COT duration and search spaceset group switching 2_1 Notifying a group of UEs of the PRB(s) and OFDMsymbol(s) where UE may assume no transmission is intended for the UE 2_2Transmission of TPC commands for PUCCH and PUSCH 2_3 Transmission of agroup of TPC commands for SRS transmissions by one or more UEs

DCI format 0_0 may be used to schedule a TB-based (or TB-level) PUSCH,and DCI format 0_1 may be used to schedule a TB-based (or TB-level)PUSCH or a CBG (Code Block Group)-based (or CBG-level) PUSCH. DCI format1_0 may be used to schedule a TB-based (or TB-level) PDSCH, and DCIformat 1_1 (DL grant DCI) may be used to schedule a TB-based (orTB-level) PDSCH or a CBG-based (or CBG-level) PDSCH. DCI format 0_0/0_1may be referred to as UL grant DCI or UL scheduling information, and DCIformat 1_0/1_1 may be referred to as DL grant DCI or UL schedulinginformation. DCI format 2_0 may be used to deliver dynamic slot formatinformation (e.g., dynamic SFI) to the UE, and DCI format 2_1 may beused to deliver downlink pre-emption information to the UE. DCI format2_0 and/or DCI format 2_1 may be delivered to the UEs in a correspondinggroup through a group common PDCCH (Group common PDCCH), which is aPDCCH delivered to the UEs defined as one group.

PDCCH/DCI includes a cyclic redundancy check (CRC), and the CRC ismasked/scrambled with various identifiers (e.g., Radio Network TemporaryIdentifier, RNTI) according to the owner or use purpose of the PDCCH.For example, if the PDCCH is for a specific UE, the CRC is masked with aC-RNTI (Cell-RNTI). If the PDCCH relates to paging, the CRC is maskedwith a Paging-RNTI (P-RNTI). If the PDCCH relates to system information(e.g., System Information Block, SIB), the CRC is masked with a SystemInformation RNTI (SI-RNTI). If the PDCCH relates to a random accessresponse, the CRC is masked with a random access-RNTI (RA-RNTI).

Table 5 illustrates the use and transport channel of the PDCCH accordingto the RNTI. The transport channel indicates a transport channel relatedto data carried by a PDSCH/PUSCH scheduled by the PDCCH.

TABLE 5 RNTI Usage Transport Channel P-RNTI Paging and SystemInformation change notification PCH(Paging Channel) SI-RNTI Broadcast ofSystem Information DL-SCH RA-RNTI Random Access Response DL-SCHTemporary C-RNTI Contention Resolution DL-SCH (when no valid C-RNTI isavailable) Temporary C-RNTI Msg3 transmission UL-SCH C-RNTI,MCS(Modulation Dynamically scheduled unicast transmission UL-SCH andCoding Scheme)-C- RNTI C-RNTI Dynamically scheduled unicast transmissionDL-SCH MCS-C-RNTI Dynamically scheduled unicast transmission DL-SCHC-RNTI Triggering of PDCCH ordered random access N/A CS(ConfiguedScheduling)- Configured scheduled umicast transmission DL-SCH, UL-SCHRNTI (activation, reactivation and retransmission) CS-RNTI Configuredscheduled unicast transmission N/A (deactivation) TPC(Transmit PowerPUCCH power control N/A Control)-PUCCH-RNTI TPC-PUSCH-RNTI PUSCH powercontrol N/A TPC-SRS-RNTI SRS trigger and power control N/AINT(Interruption)-RNTI Indication pre-emption in DL N/A SFI(Slot FormatIndication)- Slot Format Indication on the given cell N/A RNTISP(Semi-persitent)- Activation of Semi-persistent CSI reporting on PUSCHN/A CSI(Channel State Information)-RNTI

The modulation method of the PDCCH is fixed (e.g., Quadrature PhaseShift Keying, QPSK), and one PDCCH is 1, 2, 4, 8, 16 CCE (ControlChannel Element), and one PDCCH is composed of 1, 2, 4, 8, or 16 CCEs(Control Channel Elements) according to an Aggregation Level (AL). OneCCE consists of six REGs (Resource Element Groups). One REG is definedas one OFDMA symbol and one (P)RB.

A PDCCH is transmitted through a CORESET (Control Resource Set). ACORESET corresponds to a set of physical resources/parameters used tocarry PDCCH/DCI within the BWP. For example, the CORESET contains a REGset with a given numerology (e.g., SCS, CP length, etc.). The CORESETmay be configured through system information (e.g., MIB) or UE-specifichigher layer (e.g., RRC) signaling. Examples of parameters/informationused to configure the CORESET are as follows. One or more CORESETs areconfigured for one UE, and a plurality of CORESETs may overlap in thetime/frequency domain.

-   -   controlResourceSetId: it indicates identification (ID)        information of the CORESET    -   frequencyDomainResources: it indicates frequency domain resource        of the CORESET. It is indicated through a bitmap, and each bit        corresponds to an RB group (=6 consecutive RBs). For example,        the most significant bit (MSB) of the bitmap corresponds to the        first RB group in the BWP. An RB group corresponding to a bit        having a bit value of 1 is allocated as a frequency domain        resource of the CORESET.    -   duration: it indicates time domain resource of the CORESET. It        indicates the number of consecutive OFDMA symbols constituting        CORESET. For example, duration has a value of 1 to 3.    -   cce-REG-MappingType: it indicates the CCE-to-REG mapping type.        Interleaved type and non-interleaved type are supported.    -   precoderGranularity: it indicates precoder granularity in a        frequency domain    -   tci-StatesPDCCH: it indicates information(e.g., TCI-StateID)        indicating a transmission configuration indication (TCI) for the        PDCCH. The TCI state is used to provide a Quasi-Co-Location        (QCL) relationship between the DL RS(s) and the PDCCH DMRS port        in the RS set (TCI-state).    -   tci-PresentInDCI: it indicates whether the TCI field is included        in DCI.    -   pdcch-DMRS-ScramblingID: it indicates information used for        initialization of the PDCCH DMRS scrambling sequence.

For PDCCH reception, the UE may monitor a set of PDCCH candidates (e.g.,blind decoding) in CORESET. The PDCCH candidate indicates CCE(s)monitored by the UE for PDCCH reception/detection. PDCCH monitoring maybe performed in one or more CORESETs on active DL BWPs on each activatedcell in which PDCCH monitoring is configured. The set of PDCCHcandidates monitored by the UE is defined as a PDCCH search space (SS)set. The SS set may be a Common Search Space (CSS) set or a UE-specificSearch Space (USS) set.

Table 6 exemplifies a PDCCH search space.

TABLE 6 Search Space Type RNTI Use Case Type0-PDCCH Common SI-RNTI on aprimary cell Broadcast of System Information Type0A-PDCCH Common SI-RNTIon a primary cell Broadcast of System Information Type1-PDCCH CommonRA-RNTI or TC-RNTI on a primary cell Msg2, Msg4 in RACH Type2-PDCCHCommon P-RNTI as a primary cell Paging System Information changenotification Type3-PDCCH Common INT-RNTL, SFI-RNTI, TPC-PUSCH-RNTI, TPC-Group signaling PUCCH-RNTI, TPC-SRS-RNTI, C-RNTI, MCS- C-RNTI or CS-RNTIUE Specific UE Specific C-RNTI, MCS-C-RNTI or CS-RNTI UE signaling(e.g., PDSCH/PUSCH

A SS set may be configured through system information (e.g., MIB) orUE-specific higher layer (e.g., RRC) signaling. S (e.g., 10) or less SSsets may be configured in each DL BWP of the serving cell. For example,the following parameters/information may be provided for each SS set.Each SS set is associated with one CORESET, and each CORESETconfiguration may be associated with one or more SS sets.

-   -   searchSpaceId: it indicates ID of the SS set.    -   controlResourceSetId: it indicates a CORESET associated with the        SS set.    -   monitoringSlotPeriodicityAndOffset: it indicates the PDCCH        monitoring period interval (slot unit) and the PDCCH monitoring        interval offset (slot unit).    -   monitoringSymbolsWithinSlot: it indicates the first OFDMA        symbol(s) for PDCCH monitoring within a slot in which PDCCH        monitoring is configured. It is indicated through a bitmap, and        each bit corresponds to each OFDMA symbol in a slot. The MSB of        the bitmap corresponds to the first OFDM symbol in the slot.        OFDMA symbol(s) corresponding to bit(s) having a bit value of 1        corresponds to the first symbol(s) of CORESET in the slot.    -   nrofCandidates: it indicates the number of PDCCH candidates for        each AL={1, 2, 4, 8, 16} (e.g., one of 0, 1, 2, 3, 4, 5, 6, 8).    -   searchSpaceType: it indicates whether the SS type is CSS or USS.    -   DCI format: it indicates a DCI format of a PDCCH candidate

Based on the CORESET/SS set configuration, the UE may monitor PDCCHcandidates in one or more SS sets in the slot. An occasion (e.g.,time/frequency resource) to monitor PDCCH candidates is defined as aPDCCH (monitoring) occasion. One or more PDCCH (monitoring) occasionsmay be configured within a slot.

Uplink (UL) Physical Channel/Signal

(1) PUSCH

A PUSCH carries uplink data (e.g., UL-SCH TB) and/or uplink controlinformation (UC) and is transmitted based on CP-OFDM (CyclicPrefix-Orthogonal Frequency Division Multiplexing) waveform orDFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) waveform. When thePUSCH is transmitted based on the DFT-s-OFDM waveform, the UE transmitsthe PUSCH by applying transform precoding. For example, when transformprecoding is not possible (e.g., transform precoding is disabled), theUE transmits a PUSCH based on the CP-OFDM waveform, and when transformprecoding is possible (e.g., transform precoding is enabled), the UEtransmits the CP-OFDM PUSCH may be transmitted based on a waveform or aDFT-s-OFDM waveform. PUSCH may be dynamically scheduled by PDCCH orsemi-statically scheduled based on a higher layer (e.g., RRC) signaling(and/or Layer 1 (L1) signaling (e.g., PDCCH))(configured Scheduling,CS). Accordingly, in dynamic scheduling, PUSCH transmission isaccompanied by a PDCCH, but in CS, PUSCH transmission is not accompaniedby a PDCCH. CS includes Type-1 CG (Configured Grant) PUSCH transmissionand Type-2 CG PUSCH transmission. In Type-1 CG, all parameters for PUSCHtransmission are signaled by a higher layer. In Type-2 CG, some of theparameters for PUSCH transmission are signaled by a higher layer, andthe rest are signaled by the PDCCH. Basically, in CS, PDCCH is notaccompanied by PUSCH transmission.

(2) PUCCH

A PUCCH carries uplink control information (UCI). The UCI includes:

-   -   SR(Scheduling Request): it is information used to request UL-SCH        resources.    -   HARQ-ACK (Hybrid Automatic Repeat and request Acknowledgment):        it is a reception response signal for a DL signal (e.g., PDSCH,        SPS release PDCCH). The HARQ-ACK response may include positive        ACK (simply, ACK), negative ACK (NACK), DTX (Discontinuous        Transmission), or NACK/DTX. HARQ-ACK may be mixed with A/N,        ACK/NACK, HARQ-ACK/NACK, and the like. HARQ-ACK may be generated        in TB-unit/CBG-unit.

CSI (Channel status information): it is feedback information related toDL channels. The CSI includes CQI(Channel Quality Information), RI(RankIndicator), PMI(Precoding Matrix Indicator), and PTI(Precoding TypeIndicator).

Table 7 exemplifies PUCCH formats. The PUCCH format may be classifiedaccording to the UCI payload size/transmission length (e.g., the numberof symbols constituting the PUCCH resource)/transmission structure. ThePUCCH format may be classified into Short PUCCH (format 0, 2) and LongPUCCH (format 1, 3, 4) according to a transmission length.

TABLE 7 Length in PUCCH OFDM symbols Number format N_(symb) ^(PUCCH) ofbits Usage Etc 0 1-2  ≤2 HARQ, SR Sequence selection 1 4-14 ≤2 HARQ,[SR] Sequence modulation 2 1-2  >2 HARQ, CSI, [SR] CP-OFDM 3 4-14 >2HARQ, CSI, [SR] DFT-s-OFDM (no UE multiplexing) 4 4-14 >2 HARQ, CSI,[SR] DFT-s-OFDM (Pre DFT OCC)

(0) PUCCH Format 0 (PF0)

-   -   supported UCI payload sizes: up to K bits (e.g., K=2)    -   the number of OFDM symbols constituting a single PUCCH: 1˜X        symbol (e.g., X=2)    -   transmission structure: it consists of only UCI signals without        DM-RS, and transmits UCI state by selecting and transmitting one        of a plurality of sequences.

(1) PUCCH Format 1 (PF1)

-   -   supported UCI payload sizes: up to K bits (e.g., K=2)    -   the number of OFDM symbols constituting a single PUCCH: Y˜Z        symbol (e.g., Y=4, Z=14)    -   transmission structure: DM-RS and UCI are composed of different        OFDM symbols in TDM form, and UCI is a form in which a specific        sequence is multiplied by a modulation (e.g., QPSK) symbol. By        applying CS (Cyclic Shift)/OCC (Orthogonal Cover Code) to both        UCI and DM-RS (within the same RB), CDM is supported between        multiple PUCCH resources (according to PUCCH format 1).

(2) PUCCH Format 2 (PF2)

-   -   supported UCI payload sizes: more than K bits (e.g., K=2)    -   the number of OFDM symbols constituting a single PUCCH: 1˜X        symbol (e.g., X=2)    -   Transmission structure: DMRS and UCI are configured/mapped in        FDM form within the same symbol, and transmitted by applying        only IFFT without DFT to the encoded UCI bit.

(3) PUCCH Format 3 (PF3)

-   -   supported UCI payload sizes: more than K bits (e.g., K=2)    -   the number of OFDM symbols constituting a single PUCCH: Y-Z        symbol (e.g., Y=4, Z=14)    -   Transmission structure: a form in which DMRS and UCI are        configured/mapped in TDM form on different symbols, and DFT is        applied to the encoded UCI bit for transmission. OCC is applied        at the front end of DFT to UCI and CS (or IFDM mapping) is        applied to DMRS to support multiplexing to multiple UEs.

(4) PUCCH Format 4 (PF4)

-   -   supported UCI payload sizes: more than K bits (e.g., K=2)    -   the number of OFDM symbols constituting a single PUCCH: Y-Z        symbol (e.g., Y=4, Z=14)    -   Transmission structure: a structure in which DMRS and UCI are        configured/mapped in TDM form on different symbols, and DFT is        applied to encoded UCI bits to transmit without inter-terminal        multiplexing

FIG. 4 exemplifies ACK/NACK transmission procedure. Referring to FIG. 4,the UE may detect the PDCCH in slot #n. Here, the PDCCH includesdownlink scheduling information (e.g., DCI formats 1_0 and 1_1), and thePDCCH indicates a DL assignment-to-PDSCH offset (KO) and aPDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0 and1_1 may include the following information.

-   -   Frequency domain resource assignment: it indicates RB set        allocated to the PDSCH.    -   Time domain resource assignment: KO, it indicates the starting        position (e.g., OFDM symbol index) and length (e.g., number of        OFDM symbols) of the PDSCH in the slot.    -   PDSCH-to-HARQ_feedback timing indicator: it indicates K1

Thereafter, the UE may transmit the UCI through the PUCCH in the slot#(n+K1) after receiving the PDSCH in the slot #(n+K0) according to thescheduling information of the slot #n. Here, the UCI includes a HARQ-ACKresponse for the PDSCH. If the PDSCH is configured to transmit up to 1TB, the HARQ-ACK response may be configured with 1-bit. When the PDSCHis configured to transmit up to two TBs, the HARQ-ACK response may beconfigured with 2-bits when spatial bundling is not configured, and maybe configured with 1-bits when spatial bundling is configured. When theHARQ-ACK transmission time for the plurality of PDSCHs is designated asslot #(n+K1), the UCI transmitted in the slot #(n+K1) includes HARQ-ACKresponses for the plurality of PDSCHs.

1. Wireless Communication System Supporting Unlicensed Band.

FIGS. 5A and 5B illustrate an example of a wireless communication systemsupporting the unlicensed band to which the present disclosure isapplicable.

In the following description, a cell operating in a licensed band(L-band) is defined as an L-cell, and a carrier of the L-cell is definedas (DL/UL) LCC (Licensed Component Carrier). In addition, a celloperating in an unlicensed band (U-band) is defined as a U-cell, and acarrier of the U-cell is defined as (DL/UL) UCC. Thecarrier/carrier-frequency of the cell may refer to an operatingfrequency (e.g., center frequency) of the cell. A cell/carrier (e.g.,CC) is collectively referred to as a cell.

When the UE and the base station transmit and receive signals throughthe carrier combined LCC and UCC, as shown in FIG. 5A, the LCC may beconfigured to PCC (Primary CC) and UCC may be configured to SCC(Secondary CC). As shown in FIG. 5B, the UE and the base station maytransmit and receive signals through one UCC or a plurality ofcarrier-coupled UCCs. That is, the UE and the base station may transmitand receive signals through only UCC(s) without LCC. For standaloneoperation, PRACH, PUCCH, PUSCH, SRS transmission, etc. may be supportedin the UCell.

Hereinafter, the signal transmission/reception operation in theunlicensed band described in the present disclosure may be performedbased on all the above-described deployment scenarios (unless otherwisestated).

Unless otherwise stated, the following definitions may be applied toterms used in this specification.

-   -   Channel: it consists of continuous RBs in which a channel access        procedure is performed in a shared spectrum, and may refer to a        carrier or a part of a carrier.    -   CAP (Channel Access Procedure): In order to determine whether        the channel is used by other communication node(s) before signal        transmission, it is a procedure for evaluating channel        availability based on sensing. A basic unit for sensing is a        sensing slot of Ts1=9 us duration. When the base station or the        UE senses the channel during the sensing slot period, and the        detected power for at least 4 us within the sensing slot period        is less than the energy detection threshold XThresh, the sensing        slot period Tsl is considered to be in the idle state.        Otherwise, the sensing slot period Ts1=9 us is regarded as a        busy state. The CAP may be referred to as Listen-Before-Talk        (LBT).    -   Channel occupancy: After performing the channel access        procedure, it means the corresponding transmission(s) on the        channel(s) by the base station/UE.    -   COT (Channel Occupancy Time): After the base station/terminal        performs the channel access procedure, it refers to the total        time during which any base station/UE(s) sharing the channel        occupation with the base station/terminal may perform        transmission(s) on the channel. When determining the COT, if the        transmission gap is 25 us or less, the gap period is also        counted in the COT. The COT may be shared for transmission        between the base station and the corresponding terminal(s).    -   DL Transmission Burst: it is defined as the set of transmissions        from the base station, with no gaps exceeding 16 us.        Transmissions from the base station, separated by a gap greater        than 16 us, are considered separate DL transmission bursts from        each other. The base station may perform the transmission(s)        after the gap without sensing channel availability within the DL        transmission burst.    -   UL Transmission Burst: it is defined as a set of transmissions        from the UE, with no gap exceeding 16 us. Transmissions from the        UE, separated by a gap greater than 16 us, are considered as        separate UL transmission bursts from each other. The UE may        perform transmission(s) after the gap without sensing channel        availability within the UL transmission burst.    -   Discovery Burst: it refers to a DL transmission burst comprising        a set of signal(s) and/or channel(s), bound within a (time)        window and associated with a duty cycle. In an LTE-based system,        the discovery burst is transmission(s) initiated by the base        station, including PSS, SSS, and cell-specific RS (CRS), and may        further include non-zero power CSI-RS. A discovery burst in an        NR-based system is the transmission(s) initiated by the base        station, including at least an SS/PBCH block, and may further        include CORESET for PDCCH scheduling PDSCH with SIB1, PDSCH        carrying SIB1 and/or non-zero power CSI-RS.

FIG. 6 illustrates a method of occupying resources in an unlicensedband. According to regional regulation on unlicensed bands,communication nodes within unlicensed bands must determine whether othercommunication nodes use channels before transmitting signals.Specifically, the communication nodes may check whether othercommunication nodes transmit a signal by first performing carriersensing (CS) before signal transmission. A case in which it isdetermined that other communication nodes do not transmit a signal isdefined as CCA (Clear Channel Assessment) has been confirmed. If thereis a CCA threshold configured by predefined or higher layer (e.g., RRC)signaling, the communication nodes may determine the channel state asbusy if energy higher than the CCA threshold is detected in the channel,otherwise the channel state may be considered as idle. For reference, inthe Wi-Fi standard (802.11ac), the CCA threshold is defined as −62 dBmfor a non-Wi-Fi signal and −82 dBm for a Wi-Fi signal. If it isdetermined that the channel state is in an idle state, the communicationnodes may start transmitting a signal in the UCell. The above-describedseries of procedures may be referred to as LBT (Listen-Before-Talk) orCAP (Channel Access Procedure). LBT, CAP, and CCA may be expressedinterchangeably.

Specifically, for downlink reception/uplink transmission in anunlicensed band, one or more of CAP methods to be described below may beused in a wireless communication system associated with the presentdisclosure.

Downlink Signal Transmission Method Through Unlicensed Band

The base station may perform one of the following unlicensed band accessprocedures (e.g., Channel Access Procedure, CAP) for downlink signaltransmission in the unlicensed band.

(1) Type 1 Downlink CAP Method

The length of the time duration spanned by the sensing slot sensed asidle before transmission (s) in the type 1 DL CAP is random. Type 1 DLCAP may be applied to the following transmission.

-   -   transmission(s) initiated by the base station, comprising (i) a        unicast PDSCH with user plane data, or (ii) a unicast PDSCH with        user plane data and a unicast PDCCH scheduling user plane data),        or,    -   transmission(s) initiated by the base station, either (i) with a        discovery burst only, or (ii) with a discovery burst multiplexed        with non-unicast information.

FIG. 7 is a CAP operation flowchart for downlink signal transmissionthrough the unlicensed band of the base station.

Referring to FIG. 7, the base station may first sense whether thechannel is in an idle state during the sensing slot period of the deferduration Td, and then when the counter N becomes 0, transmission may beperformed (S1234). At this time, the counter N is adjusted by sensingthe channel during additional sensing slot period(s) according toprocedure below:

Step 1) (S1220) set N=Ninit. Here, Ninit is a random value uniformlydistributed between 0 and CWp. Then go to step 4.

Step 2) (S1240) if N>0 and the base station decides to decrement thecounter, set N=N−1

Step 3) (S1250) the channel is sensed during the additional sensing slotperiod. At this time, if the additional sensing slot period is idle (Y),the process moves to step 4. If not (N), go to step 5.

Step 4) (S1230) if N=0 (Y), the CAP procedure ends (S1232). Otherwise(N), go to step 2.

Step 5) (S1260) the channel is sensed until a busy sensing slot isdetected within the additional defer duration Td, or all sensing slotswithin the additional defer duration Td are detected as idle (idle).

Step 6) (S1270) if the channel is sensed as idle during all sensing slotperiods of the additional defer duration Td, go to step 4. If not (N),go to step 5.

Table 8 shows that mp applied to CAP, minimum contention window (CW),maximum CW, maximum channel occupancy time (MCOT) and allowed CW sizesvary according to the channel access priority class.

TABLE 8 Channel Access Priority allowed Class (p) m_(p) CW_(min, p)CW_(max, p) T_(mcot, p) CW_(p) size 1 1 3 7 2 ms {3, 7}  2 1 7 15 3 ms{7, 15} 3 3 15 63 8 or {15, 31, 63} 10 ms 4 7 15 1023 8 or {15, 31, 63,127, 10 ms 255, 511, 1023}

The defer duration Td is configured in the order of the period Tf (16us)+mp consecutive sensing slot period Tsl (9 us). Tf includes thesensing slot period Tsl at the start time of the 16 us period.

CWmin,p<=CWp<=CWmax,p. CWp may be configured as CWp=CWmin,p, and may beupdated before step 1 based on HARQ-ACK feedback (e.g., ACK or NACKratio) for the previous DL burst (e.g., PDSCH) (CW size update). Forexample, CWp may be initialized to CWmin,p based on the HARQ-ACKfeedback for the previous DL burst, may be increased to the next highestallowed value, or the existing value may be maintained.

(2) Type 2 Downlink (DL) CAP Method

The length of time duration spanned by the sensing slot sensed as idlebefore transmission (s) in the type 2 DL CAP is deterministic(deterministic). Type 2 DL CAPs are classified into Type 2A/2B/2C DLCAPs.

Type 2A DL CAP may be applied to the following transmission. In Type 2ADL CAP, the base station may transmit transmission immediately after thechannel is sensed as idle for at least the sensing period Tshort_dl=25us. Here, Tshort_dl consists of a period Tf(=16 us) and one sensing slotperiod immediately following. Tf includes a sensing slot at thebeginning of the duration.

-   -   transmission(s) initiated by the base station, (i) with only a        discovery burst, or (ii) with a discovery burst multiplexed with        non-unicast information, or;    -   transmission(s) of the base station after a 25 us gap from the        transmission(s) by the UE within a shared channel occupancy.

Type 2B DL CAP may be applicable to transmission (s) performed by thebase station after a 16 us gap from the transmission (s) by the UEwithin the shared channel occupation time. In Type 2B DL CAP, the basestation may transmit transmission immediately after the channel issensed as idle for Tf=16 us. Tf includes a sensing slot within the last9 us of the duration. Type 2C DL CAP may be applicable totransmission(s) performed by the base station after a maximum of 16 usgap from transmission(s) by the UE within the shared channel occupationtime. In Type 2C DL CAP, the base station does not sense the channelbefore performing transmission.

Uplink Signal Transmission Method Through the Unlicensed Band

The UE performs a Type 1 or Type 2 CAP for uplink signal transmission inthe unlicensed band. In general, the UE may perform a CAP (e.g., type 1or type 2) configured by the base station for uplink signaltransmission. For example, the UE may include CAP type indicationinformation in a UL grant (e.g., DCI formats 0_0, 0_1) for schedulingPUSCH transmission.

(1) Type 1 Uplink (UL) CAP Method

The length of time duration spanned by the sensing slot sensed as idlebefore transmission (s) in the type 1 DL CAP is random. Type 1 UL CAPmay be applied to the following transmission.

-   -   PUSCH/SRS transmission(s) configured and/or scheduled from the        base station.    -   PUCCH transmission(s) configured and/or scheduled from the base        station.    -   random access procedure (RAR) related to transmission(s)

FIG. 8 is a flow chart of the Type 1 CAP operation of the UE for uplinksignal transmission.

Referring to FIG. 8, the UE first may sense whether the channel is in anidle state during the sensing slot period of the defer duration Td, andthen when the counter N becomes 0, transmission may be performed(S1534). At this time, the counter N is adjusted by sensing the channelduring the additional sensing slot period(s) according to the procedurebelow:

Step 1) (S1520) Set N=Ninit. Here, Ninit is a random value uniformlydistributed between 0 and CWp. Then go to step 4.

Step 2) (S1540) If N>0 and the UE decides to decrement the counter, setN=N−1.

Step 3) (S1550) The channel is sensed during the additional sensing slotperiod. At this time, if the additional sensing slot period is idle (Y),the process moves to step 4. If not (N), go to step 5.

Step 4) (S1530) If N=0 (Y), the CAP procedure is terminated (S1532).Otherwise (N), go to step 2.

Step 5) (S1560) The channel is sensed until a busy sensing slot isdetected in the additional defer duration Td, or all sensing slots inthe additional defer duration Td are detected as idle (idle).

Step 6) (S1570) If the channel is sensed as idle during all sensing slotperiods of the additional defer duration Td (Y), it moves to step 4. Ifnot (N), go to step 5.

Table 9 shows that mp applied to CAP, minimum contention window (CW),maximum CW, maximum channel occupancy time (MCOT) and allowed CW sizesvary according to the channel access priority class.

TABLE 9 Channel Access Priority allowed Class (p) m_(p) CW_(min, p)CW_(max, p) T_(ulmcot, p) CW_(p) size 1 2 3 7 2 ms {3, 7}  2 2 7 15 4 ms{7, 15} 3 3 15 1023 6 ms or {15, 31, 63, 127, 10 ms 255, 511, 1023} 4 715 1023 6 ms or {15, 31, 63, 127, 10 ms 255, 511, 1023}

The defer duration Td is configured in the order of the period Tf (16us)+mp consecutive sensing slot period Tsl (9 us). Tf includes thesensing slot period Tsl at the start time of the 16 us period.

CWmin,p<=CWp<=CWmax,p. CWp is configured as CWp=CWmin,p, and may beupdated before step 1 based on an explicit/implicit reception responseto a previous UL burst (e.g., PUSCH) (CW size update). For example, CWpmay be initialized to CWmin,p based on an explicit/implicit receptionresponse to the previous UL burst, may be increased to the next highestallowed value, or the existing value may be maintained.

(2) Type 2 Uplink (UL) CAP Method

The length of the time duration spanned by a sensing slot sensed as idlebefore transmission (s) in a Type 2 UL CAP is deterministic(deterministic). Type 2 UL CAPs are classified into Type 2A/2B/2C ULCAPs. In Type 2A UL CAP, the UE may transmit transmission immediatelyafter the channel is sensed as idle for at least the sensing periodTshort_dl=25 us. Here, Tshort_dl consists of a section Tf (=16 us) andone sensing slot period immediately following. In Type 2A UL CAP, Tfincludes a sensing slot at the beginning of the duration. In Type 2B ULCAP, the UE may transmit transmission immediately after the channel issensed as idle for the sensing period Tf=16 us. In Type 2B UL CAP, Tfincludes a sensing slot within the last 9 us of the duration. In Type 2CUL CAP, the UE does not sense a channel before performing transmission.

RB Interlace

FIG. 9 illustrates an RB interlace. In the shared spectrum, inconsideration of OCB (Occupied Channel Bandwidth) and PSD (PowerSpectral Density) related regulations, a set of (single) discontinuous(single) RBs (at equal intervals) on a frequency may be defined as aunit resource used/allocated for UL (physical) channel/signaltransmission. Such a discontinuous RB set is defined as “RB interlace”(simply, interlace) for convenience.

Referring to FIG. 9, a plurality of RB interlaces (simply, interlaces)may be defined within a frequency band. Here, the frequency band mayinclude a (wideband) cell/CC/BWP/RB set, and the RB may include a PRB.For example, interlace #m∈{0, 1, . . . , M−1} may consist of (common) RB{m, M+m, 2M+m, 3M+m, . . . }. M represents the number of interlaces. Atransmitter (e.g., a UE) may transmit a signal/channel using one or moreinterlaces. The signal/channel may include PUCCH or PUSCH.

2. Random Access (RA) Procedure

FIGS. 10A and 10B show a random access procedure. FIG. 10A shows acontention-based random access procedure, and FIG. 10B illustrates adedicated random access procedure.

Referring to FIG. 10A, the contention-based random access procedureincludes the following steps. Hereinafter, the message transmitted insteps 1 to 4 may be referred to as messages (Msg) 1 to 4, respectively.

-   -   Step 1: the UE transmits a RACH preamble through a RPACH.    -   Step 2: the UE receives a random access response (RAR) from the        base station through the DL-SCH.    -   Step 3: the UE transmits layer 2/layer 3 message to the base        station through the UL-SCH.    -   Step 4: the UE receives a contention resolution message from the        base station through the DL-SCH.

The UE may receive information on the random access from the basestation through system information.

If random access is required, the UE transmits the RACH preamble to thebase station as in step 1. The base station may distinguish each randomaccess preamble through a time/frequency resource (RACH Occasion; RO)and a random access preamble index (PI) in which the random accesspreamble is transmitted.

When the base station receives the random access preamble from the UE,the base station transmits the random access response (RAR) message tothe UE as in step 2. For the reception of the random access message, theUE monitors the L1/L2 control channel (PDCCH) with CRC masked by RA-RNTI(random access-RNTI), including scheduling information on a randomaccess response message, within a preconfigured time window(e.g.,ra-ResponseWindow). PDCCH masked with RA-RNTI may be transmitted onlythrough a common search space. When receiving the scheduling signalmasked by the RA-RNTI, the UE may receive a random access responsemessage from the PDSCH indicated by the scheduling information.Thereafter, the UE checks whether there is random access responseinformation indicated to it in the random access response message.Whether or not random access response information indicated to itselfexists may be checked by whether a random access preamble ID (RAPID) fora preamble transmitted by the UE exists. The index and RAPID of thepreamble transmitted by the UE may be the same. The random accessresponse information includes a corresponding random access preambleindex, timing offset information for UL synchronization (e.g., TimingAdvance Command, TAC), UL scheduling information for message 3transmission (e.g., UL grant) and terminal temporary identificationinformation (e.g., Temporary-C-RNTI, TC-RNTI).

The UE receiving the random access response information, as in step 3,transmits UL-SCH(shared channel) data(message 3) through the PUSCHaccording to the UL scheduling information and the timing offset value.The message 3 may include the ID of the UE(or, the global ID of the UE).Alternatively, the message 3 may include information related to RRCconnection request(e.g., RRCSetupRequest message) for initial access. Inaddition, the message 3 may include a buffer status report(BSR) on theamount of data available for transmission by the UE.

After receiving UL-SCH data, as in step 4, the base station transmits acontention resolution message (message 4) to the UE. When the UEreceives the contention resolution message and the contention isresolved successfully, the TC-RNTI is changed to the C-RNTI. Message 4may include the ID of the UE and/or RRC connection related information(e.g., an RRCSetup message). If the information transmitted through themessage 3 and the information received through the message 4 do notmatch, or if the message 4 is not received for a certain period of time,the UE may retransmit the message 3 as the contention resolution hasfailed.

Referring to FIG. 10B, the dedicated random access procedure includesthe following 3 steps. Hereinafter, the messages transmitted in steps 0to 2 may be referred to as messages (Msg) 0 to 2, respectively. Thededicated random access procedure may be triggered using a PDCCH(hereinafter referred to as a PDCCH order) for instructing the basestation to transmit the RACH preamble.

-   -   Step 0: the base station allocates a RACH preamble through the        dedicated signaling to the UE.    -   Step 1: the UE transmits the RACH preamble through the PRACH.    -   Step 2: the UE receives a random access response (RAR) through        DL-SCH from the base station through the DL-SCH.

Operations of steps 1 and 2 of the dedicated random access procedure maybe the same as step 1 and 2 of the contention-based random accessprocedure.

In NR, DCI format 1_0 is used to initiate a non-contention-based randomaccess process with a PDCCH command (order). DCI format 1_0 is used toschedule a PDSCH in one DL cell. On the other hand, when the CRC (CyclicRedundancy Check) of DCI format 1_0 is scrambled with C-RNTI and all bitvalues of the “Frequency domain resource assignment” field are 1, DCIformat 1_0 is used as a PDCCH order indicating a random accessprocedure. In this case, the field of DCI format 1_0 is configured asfollows.

-   -   RA preamble index: 6 bit    -   UL/SUL(Supplementary UL) indicator: 1 bit. When the bit values        of the RA preamble index are not all 0 and SUL is configured in        the cell for the UE, it indicates the UL carrier on which the        PRACH is transmitted in the cell. Otherwise, it is reserved.    -   SSB (Synchronization Signal/Physical Broadcast Channel) index: 6        bit. When all bit values of the RA preamble index are not 0, it        indicates the SSB used to determine the RACH opportunity for        PRACH transmission. Otherwise, it is reserved.    -   PRACH mask index: 4 bit. When all bit values of the RA preamble        index are not 0, it indicates the RACH occasion associated with        the SSB indicated by the SSB index. Otherwise, it is reserved.    -   Reserved: 10 bit.

When the DCI format 1_0 does not correspond to the PDCCH order, the DCIformat 1_0 consists of fields used to schedule the PDSCH (e.g., timedomain resource assignment, MCS (Modulation and Coding Scheme), HARQprocess number, PDSCH-to-HARQ_feedback timing indicator and the like).

2-Step Random Access Procedure

As described above, the conventional random access goes through afour-step procedure. In the conventional LTE system, as shown in Table10, an average of 15.5 ms was required for the four-step random accessprocedure.

TABLE 10 Component Description Time (ms) 1 Average delay due to RACHscheduling period (1 ms RACH cycle) 0.5 2 RACH Preamble 1 3-4 Preambledetection and transmission of RA response (Time between the end 3 RACHtransmission and UE's reception of scheduling grant and timingadjustment) 5 UE Processing Delay (decoding of scheduling grant, timingalignment and C- 5 RNTI assignment + L1 encoding of RRC ConnectionRequest) 6 Transmission of RRC and NAS Request 1 7 Processing delay ineNB (L2 and RRC) 4 8 Transmission of RRC Connection Set-up (and ULgrant) 1

In NR system, lower latency than the existing system may be required. Inaddition, if the random access procedure occurs in the U-band, therandom access procedure is terminated and contention is resolved onlywhen the UE and the base station sequentially succeed in LBT in both the4-step random access procedure. If the LBT fails even in one step of the4-step random access procedure, resource efficiency is reduced andlatency is increased. In particular, if the LBT fails in thescheduling/transmission procedure associated with message 2 or message3, a decrease in resource efficiency and an increase in latency mayoccur significantly. Even a random access procedure in the L-band mayrequire a low-latency random access process in various scenarios of anNR system. Accordingly, the 2-step random access procedure may beperformed on the L-band as well.

As shown in FIG. 11A, the 2-step random access procedure may consist oftwo steps of uplink signal (referred to as message A) transmission fromthe UE to the base station and downlink signal (referred to as messageB) transmission from the base station to the UE.

The following description focuses on the initial access process, but thefollowing proposed method may be equally applied to the random accessprocess after the RRC connection between the UE and the base station ismade. Also, in the non-contention random access process, as shown inFIG. 11B, the random access preamble and the PUSCH part may betransmitted together.

Although not shown, a PDCCH for scheduling message B may be transmittedfrom the base station to the terminal, which is Msg. It may be referredto as B PDCCH.

3. Random Access Procedure in the Unlicensed Band

The above-mentioned contents (3GPP system(or NR system), framestructure, etc.) may be applied in combination with the methods proposedin the present disclosure to be described later, or the technicalcharacteristics of the methods proposed in the present disclosure may beclearly described may be supplemented.

As described above, in the Wi-Fi standard (802.11ac), the CCA thresholdis defined as −62 dBm for a non-Wi-Fi signal and −82 dBm for a Wi-Fisignal. In other words, when a signal from a device not belonging to theWi-Fi system is received with a power of −62 dBm or higher in a specificband, the STA (Station) or AP (Access Point) of the Wi-Fi system doesnot transmit signals in the specific band.

PRACH (Physical Random Access Channel) format includes a Long RACHformat and a short RACH format. The PRACH corresponding to the Long RACHformat consists of a length 839 sequence. The PRACH corresponding to theShort RACH format consists of a 139-length sequence. Hereinafter, astructure of a sequence constituted by the Short RACH format isproposed. In the FR1 (Frequency Range 1) band of less than 6 GHz, theSCS of the Short RACH format corresponds to 15 and/or 30 KHz. The PRACHcorresponding to the Short RACH format may be transmitted through 12 RBsas shown in FIGS. 10A and 10B. 12 RBs include 144 REs, and PRACH may betransmitted on 139 tones (139 REs) of 144 REs. In FIG. 12, two REs inthe order of the lowest index and three REs in the order of the highestindex of the 144 REs correspond to null tones, but the positions of thenull tones may be different from those shown in FIG. 12.

In the present disclosure, the Short RACH format may be referred to as aShort PRACH format, and the Long RACH format may be referred to as aLong PRACH format. The PRACH format may be referred to as a preambleformat.

The short PRACH format may consist of values defined in Table 11.

TABLE 11 Format L_(RA) Δf^(RA) N_(u) N_(CP) ^(RA) A1 139 15 × 2^(μ) kHz2 × 2048κ × 2^(−μ) 288κ × 2^(−μ) A2 139 15 × 2^(μ) kHz 4 × 2048κ ×2^(−μ) 576κ × 2^(−μ) A3 139 15 × 2^(μ) kHz 6 × 2048κ × 2^(−μ) 864κ ×2^(−μ) B1 139 15 × 2^(μ) kHz 2 × 2048κ × 2^(−μ) 216κ × 2^(−μ) B2 139 15× 2^(μ) kHz 4 × 2048κ × 2^(−μ) 360κ × 2^(−μ) B3 139 15 × 2^(μ) kHz 6 ×2048κ × 2^(−μ) 504κ × 2^(−μ) B4 139 15 × 2^(μ) kHz 12 × 2048κ × 2^(−μ) 936κ × 2^(−μ) C0 139 15 × 2^(μ) kHz 2048κ × 2^(−μ) 1240κ × 2^(−μ)  C1139 15 × 2^(μ) kHz 4 × 2048κ × 2^(−μ) 2048κ × 2^(−μ) 

In the Table 11, LRA is the length of sequence, ΔfRA is the SCS appliedto RACH, AND k is Ts/Tc=64. As μ∈{0,1,2,3}, μ is determined as one of 0,1, 2, and 3 according to the SCS value. For example, μ is set to 0 for15 kHz SCS, and μ is set to 1 for 30 kHz SCS.

The base station may inform, through higher layer signaling, which thePRACH format can be transmitted at a specific timing for a specificperiod (duration), and up to how many ROs are in the corresponding slot.Table 6.3.3.2-2 to Table 6.3.3.2-4 of the 38.211 standard correspond tothis. Table 12 shows only a few specific excerpts from the indexes thatmay use A1, A2, A3, B1, B2, B3 alone or in combination in Table6.3.3.2-3 of the 38.211 standard.

TABLE 12 N_(t) ^(RA, slot), number of time- Number of domain PRACH PRACHPRACH slots occasions N_(dur) ^(RA), Configuration Preamble n_(SFN) modx = y Subframe Starting within a within a PRACH Index format x y numbersymbol subframe PRACH slot duration 81 A1 1 0 4, 9 0 1 6 2 82 A1 1 0 7,9 7 1 3 2 100 A2 1 0 9 9 1 1 4 101 A2 1 0 9 0 1 3 4 127 A3 1 0 4, 9 0 12 6 128 A3 1 0 7, 9 7 1 1 6 142 B1 1 0 4, 9 2 1 6 2 143 B1 1 0 7, 9 8 13 2 221 A1/B1 1 0 4, 9 2 1 6 2 222 A1/B1 1 0 7, 9 8 1 3 2 235 A2/B2 1 04, 9 0 1 3 4 236 A2/B2 1 0 7, 9 6 1 2 4 251 A3/B3 1 0 4, 9 0 1 2 6 252A3/B3 1 0 7, 9 2 1 2 6

As shown in FIG. 12, it may to know how many ROs are defined in the RACHslot for each preamble format (the number of time-domain PRACH occasionswithin a PRACH slot of Table 12) and how many OFDM (orthogonalfrequency-division multiplexing) symbols are occupied (PRACH duration ofTable 12) by the PRACH preamble of each preamble format (PRACH durationin Table 12). In addition, since the starting symbol of the first RO maybe indicated for each preamble format, information on from which pointin the corresponding RACH slot the RO starts may be transmitted/receivedbetween the base station and the UE. FIG. 13 shows a configuration of anRO in a RACH slot for each PRACH configuration index value of Table 12.

On the other hand, the device operating in the unlicensed band checkswhether a channel to transmit a signal is in an idle state or a busystate. When a channel is in an idle state, a signal is transmittedthrough the corresponding channel. When the channel is in the busystate, the device to transmit the signal waits until the channel becomesthe idle state before transmitting the signal. As previously describedthrough FIGS. 6 and 7, such an operation may be referred to as an LBT orchannel access scheme. In addition, there may be LBT categories(category) as shown in Table 13.

TABLE 13  The channel access schemes for NR-based access for unlicensedspectrum can be classified into the following categories:    - Category1: Immediate transmission after a short switching gap     - This is usedfor a transmitter to immediately transmit after a switching gap   insidea COT.     - The switching gap from reception to transmission is toaccommodate the   transceiver turnaround time and is no longer than 16μs.    - Category 2: LBT without random back-off     - The duration oftime that the channel is sensed to be idle before the transmitting  entity transmits is deterministic.    - Category 3: LBT with randomback-off with a contention window of fixed size     - The LBT procedurehas the following procedure as one of its components. The   transmittingentity draws a random number N within a contention window. The size of  the contention window is specified by the minimum and maximum value ofN. The size   of the contention window is fixed. The random number N isused in the LBT procedure   to determine the duration of time that thechannel is sensed to be idle before the   transmitting entity transmitson the channel.    - Category 4: LBT with random back-off with acontention window of variable size     -The LBT procedure has thefollowing as one of its components. The transmitting   entity draws arandom number N within a contention window. The size of contention  window is specified by the minimum and maximum value of N. Thetransmitting entity   can vary the size of the contention window whendrawing the random number N. The   random number N is used in the LBTprocedure to determine the duration of time that   the channel is sensedto be idle before the transmitting entity transmits on the channel.

LBT corresponding to category 1 is a method of accessing a channelwithout LBT. According to the LBT corresponding to the specific category1, after the specific node occupies the channel, if the time intervaluntil just before the next transmission is less than 16 us, the specificnode may access the channel regardless of the state. Next, category 2LBT is a method of accessing a channel after performing one-shot LBTwithout a back-off counter value. According to the LBT corresponding tocategory 2, a specific node performs transmission after determiningwhether a channel is idle for 16 us (or 25 us).

For LBT corresponding to the category 3 and the category 4, a backoffcounter value is randomly selected within a contention window (CW). Inthis present disclosure, the LBT corresponding to the category 3 may bereferred to as a Cat 3 LBT, and the LBT corresponding to the category 4may be referred to as Cat 4 LBT. For the LBT corresponding to thecategory 3, a back-off counter value is selected randomly based on thealways fixed contention window size value. For the LBT corresponding tothe category 4, the contention window size value is increased by 1 stepin the allowed candidates each time the LBT fails, starting from thefirst minimum contention window size value. Candidates for the maximumvalue, the minimum value, and the allowed contention window size valueof the contention window size are predefined for each channel accesspriority class (see Tables 3 and 4). For example, for Cat 4 LBT having achannel access priority class of 4, the UE initially selects a backoffcounter value randomly from 0 to 15. If the UE fails the LBT, the UErandomly selects a backoff counter value from 0 to 31.

The LBT corresponding to the LBT may include a type 2C DL CAP and a type2C UL CAP as described above. The LBT corresponding to the category 2may include a type 2A DL CAP, a type 2B DL CAP, and a type 2B UL CAP.The LBT corresponding to the category 4 may include a type 1 DL CAP anda type 1 UL CAP.

The UE selecting the back-off counter value based the values defined inTable 9, if the channel is idle for 16+9×mp+K×9 us, performs an uplinktransmission indicated and/or configured from the base station. K is theselected backoff counter value, and mp corresponds to the slot timeapplied according to the channel access priority class. The channelaccess priority class and LBT category for PRACH transmission may be asshown in Table 14.

TABLE 14 Cat 2 LBT Cat 4 LBT PUSCH (including at N/A except for theChannel access priority least UL-SCH with cases discussed in class isselected according user plane data) Note 2 below to the data SRS-onlyN/A Cat4 with lowest channel access priority class value (as in LTEeLAA) RACH-only (see Note 2) Cat4 with lowest channel access priorityclass value PUCCH-only (see Note 2) Cat4 with lowest channel accesspriority class value Note 2: Applicability of 3 chanrel access schemeother than Cat 4 for the following signals/channels have been discussedand details are to be determined when the specifications are developed:UL control information including UCI only on PUSCH, e.g. HARQ-ACK,Scheduling Request, and Channel State Information Random Access

Based on the values that can be derived through Tables 13 and 14, the UEmay start PRACH transmission if the channel is idle for16+9*2+K*9=34+K*9 (us). As described above, the backoff counter value Kis randomly selected within the size-varying contention window sizevalue.

The above-described 2-step random access procedure consist oftransmission of message A (Msg. A; PRACH preamble and Msg. 3 PUSCH) ofthe UE, and transmission of message B (Msg. B; RAR and Msg. 4 PDSCH) ofthe base station. For convenience of description, in the presentdisclosure, the time and frequency resource to which the PRACH preamblesignal of Msg. A is mapped/transmitted is defined as RO (RACH Occasion),and the time and frequency resource to which a Msg. 3 PUSCH signal ismapped/transmitted is defined as PO (PUSCH Occasion). Hereinafter, aspecific method for configuring Msg. A is proposed. The RACH preambleconstituting Msg. A may be referred to as Msg. A RACH preamble and Msg.A PRACH. The Msg. 3 PUSCH constituting Msg. A may be referred to as Msg.A PUSCH. The RAR constituting Msg. B may be referred to as Msg. B. TheMsg. 4 PDSCH constituting Msg. B may be referred to as The Msg. B PDSCH.

In particular, in NR-U, the operation for the UE's channel accessprocedure (channel access procedure) to transmit Msg. A in the RO and POneeds to be defined. Accordingly, the present disclosure proposes achannel access procedure according to time/frequency resources of RO andPO and a timing gap between RO and PO. For convenience of description,parameters for time/frequency resources of RO and PO and a time intervalbetween RO and PO are defined as shown in FIG. 14. That is, according toFIG. 14, Ti means a time duration of RO, T2 means a time duration of PO,T means T1+T2, F1 means a frequency bandwidth of RO, F2 means afrequency band of PO, and P1 means a time interval between RO and PO.

Hereinafter, an operation of the UE for performing channel access usingchannel occupancy sharing, proposed in the present disclosure, will bedescribed.

(1) First, the UE receives control information related to the RO and/orPO from the base station. Here, the control information may includeparameters shown in FIG. 14. (2) Next, the UE determines the LBT type tobe performed in front of the RO and/or PO based on the controlinformation. (3) Next, the UE transmits an Msg. A preamble and/or Msg. APUSCH in the RO and/or PO based on the determined LBT type.

For more detailed information, refer to methods to be described later.That is, the methods to be described later may be combined with theprocedures of (1) to (3) above to achieve the object/effect proposed inthe present disclosure. In addition, the methods to be described latermay be combined with the procedure described in the 2 random accessprocess to achieve the object/effect proposed in the present disclosure.In this present disclosure, ‘unlicensed band’ may be substituted andmixed with ‘shared spectrum’. Also, in this present disclosure, ‘LBTtype’ may be substituted and mixed with ‘channel access type’. ‘LBT’ maybe substituted and mixed with ‘channel access’.

3.1 EMBODIMENT 1 Channel Access Procedure Considering Channel OccupancySharing

As a first method, a channel access operation for a method in which theUE considers channel occupancy (CO) sharing for Msg. A preamble and Msg.A PUSCH transmission is as follows. At this time, the reason forconsidering the CO sharing is that if the CO sharing is not performed,Cat-4 LBT (random back-off based) must be performed before alltransmissions. That is, through the CO sharing, the LBT process otherthan the first LBT process may be Cat-1 LBT (no LBT) or Cat-2 LBT (oneshot LBT). Therefore, channel access may be performed more quickly andeasily. The parameters used in the following description are shown inFIG. 14.

Referring to Table 9, the CO sharing time (Tulmcotp) is definedaccording to priority class (PC). That is, if the PC is 1, the COsharing time is 2 ms or less, if the PC is 2, the CO sharing time is 4ms or less, and if the PC is 3 or 4, the CO sharing time is 6 ms or 10ms or less (whether Ems or 10 ms is determined by higher layersignaling). Therefore, the next operation may be divided into thefollowing three durations according to the CO sharing time and PC.

Duration 1: 0 ms<T<=2 ms, in this case, PCRO may be 1 for CO sharing.

Duration 2: 2 ms<T<=4 ms, in this case, PCRO may be 2 for CO sharing.

Duration 3: 4 ms<T<=6 ms (or, 10 ms), in this case, PCRO may be 4 or 4for CO sharing.

For each duration defined above, the UE may perform the followingoperation.

1-1. For each interval, the UE performs Cat-4 LBT using the priorityclass PCRO in front of the Msg A preamble (RACH) occasion (RO). Aftersuccessful LBT, the UE transmits Msg A preamble,

1-1-A. If P1<16(us), since the CO sharing is possible, the UE performsCat-1 LBT (i.e., no LBT) in front of the Msg. A PUSCH occasion (P0).

1-1-B. Otherwise, if the P1 is 16 (us),

if T2>X, since the CO sharing is possible, the UE performs Cat-2 LBT(i.e., 16 (us) one shot LBT) in front of the PO. X is the maximum timingduration allowed for UL signal/channel transmission without performingLBT operation. This may be indicated by the base station through higherlayer signaling (e.g., SIB or RMSI (remaining minimum systeminformation), etc.). For example, X may be 0.5 ms.

If the T2<=X, since the CO sharing is possible, the UE performs Cat-1LBT (i.e., no LBT) in front of the PO.

1-1-C. Otherwise, if the P1 is 25 (us), since the CO sharing ispossible, the UE performs Cat-2 LBT (i.e., 25 (us) one shot LBT) infront of the PO.

1-1-D. Otherwise, if the P1 is more than 25 (us),

if the CO sharing is allowed, the UE performs Cat-2 LBT (i.e., 25 (us)one shot LBT) or Cat-4 LBT indicated through the higher layer signaling(e.g., SIB or RMSI etc.). Priority class PC_(PO) (e.g., PC_(PO) may bethe same as PC_(RO)) used by the UE performing Cat-4 LBT in front of thePO may be promised in advance or may be indicated through the higherlayer signaling (e.g., SIB or RMSI etc.) by the base station.

If CO sharing is not allowed, the UE performs Cat-4 LBT in front of thePO. Priority class PC_(PO) (e.g., PC_(PO) may be the same as thePC_(RO)) used by the UE performing Cat-4 LBT in front of the PO may bepromised in advance, or may be indicated by the base station throughhigher layer signaling (e.g., SIB or RMSI).

Characteristically, an upper limit of PI that may perform Cat-2 LBT maybe configured. The base station may configure the upper limit of P1 thatmay perform Cat-2 LBT to the UE through higher layer signaling (e.g.,SIB or RMSI, etc.) (or defined in the specification), and the UE maydetermine the LBT type by comparing the upper limit value of the P1 withthe current P1 value and perform a channel access procedure. Forexample, if the upper limit of the P1 that may perform Cat-2 LBT isP1MAX, if the P1 is smaller than P1MAX, the UE may perform Cat-2 LBT infront of the PO. If the P1 is greater than P1MAX, the UE may performCat-4 LBT in front of the PO. In this case, the priority class PC_(PO)(e.g., PC_(PO) may be the same as PC_(RO)) used by the UE may bepromised in advance, or may be indicated by the base station throughhigher layer signaling (e.g., SIB or RMSI, etc.).

The base station may also indicate whether the CO sharing is allowedthrough higher layer signaling (e.g., SIB or RMSI, etc.).

1-2. The operation of embodiment 1 may be applied when F1 and F2 existin the same LBT sub-band, and/or when F1 includes F2.

3.2 EMBODIMENT 2 Channel Access Procedure Without Considering ChannelOccupancy Sharing

A proposal of a channel access operation for a method in which the UEdoes not consider CO sharing for Msg. A preamble and Msg A. PUSCHtransmission is as follows. The parameters used in the followingdescription are shown in FIG. 14. Also in embodiment 2, the followingthree time duration, described in Embodiment 1, may be applied.

Duration 1: 0 ms<T<=2 ms, in this case, PC_(RO) may be 1 for CO sharing.

Duration 2: 2 ms<T<=4 ms, in this case, PC_(RO) may be 2 for CO sharing.

Duration 3: 4 ms<T<=6 ms (or, 10 ms), in this case, PC_(RO) may be 3 or4 for CO sharing.

For each duration defined above, the UE may perform the followingoperation.

2-1. For each duration, even if T is greater than the maximum value ofeach duration (because CO sharing is not considered), the UE performsCat-4 LBT using the priority class PC_(RO) in front of Msg. A preambleRO. The maximum value of each duration may be, for example, 2 ms inDuration 1, 4 ms in Duration 2, and 6 ms (or 10 ms) in Duration 3.PC_(RO) may be 1 when T is greater than 2 ms, PC_(RO) may be 1 or 2 whenT is greater than 4 ms, and PC_(RO) may be 1, 2, 3, or 4 when T isgreater than 6ms (or 10 ms). After successful LBT, the UE transmits Msg.A preamble,

2-1-A. (Because CO sharing is not considered), the UE performs Cat-4 LBTin front of the PO. The priority class, PCPO (e.g., PCPO may be the sameas PCRO) used by the UE performing Cat-4 LBT in front of the PO may bepromised in advance, or may be indicated by the base station throughhigher layer signaling (e.g., SIB or RMSI, etc.).

2-2. Additionally, F1 and F2 do not exist in the same LBT sub-band,and/or F1 does not include F2, the UE is configured to perform Cat-4 LBTin front of PO

If the FBE (frame based equipment) configuration or the LBT before theRO is configured to Cat-2 LBT, the LBT before the PO may be alsoconfigured to Cat 2-LBT or configured to apply the same rule as RO.

3.3 EMBODIMENT 3 LBT Type Configuration for A/N Feedback Transmission ofMsg. B

Next, upon receiving a message (e.g., RRC connection setup, etc.)indicating that the RACH procedure has been successful through the MACCE of Msg. B, etc. from the base station, the UE needs to transmit anA/N feedback (e.g., ACK) for it. In front of the PUCCH resource for A/Nfeedback transmission, the UE needs to perform LBT, and a method ofdetermining the corresponding LBT type may be as follows.

3-1. Method in which all UE receiving Msg. B are instructed by a commonLBT type

3-1-A. Opt 1) Indicate the LBT type in common to all UEs (or group ofUEs) through the PDCCH (e.g., DCI field, etc.) that the base stationschedules the PDSCH carrying Msg. B

When configured in this way, among the UEs receiving the correspondingMsg. B, the UE that needs to transmit the A/N feedback may be instructedwith the same LBT type through the corresponding PDCCH (e.g., specificDCI field), and may perform a channel access procedure using theindicated LBT type (e.g., Cat-2 LBT).

If the base station divides the UE into N(e.g., N=2) groups through aspecification criteria, and indicates different LBT types to the N(e.g., N=2) groups for a specific reason (e.g., whether the base stationsuccessfully received Msg B), the LBT type corresponding to each groupis used. UEs belonging to a specific group may perform a channel accessprocedure using the same LBT type.

Different LBT types may be indicated using an independent DCI field andthe like. If the base station indicates the LBT type for one groupthrough a specific DCI field, the LBT type of the other group may bedetermined as the LBT type promised in advance according to theindicated DCI field.

3-1-B. Opt2) the base station indicates the LTB type in common to allUEs (or, group of UE), by adding a common field to the PDSCH(e.g., theheader part of MAC CE) carrying Msg. B.

If configured as 3-1-B, among the UEs receiving Msg. B, the UE thatneeds to transmit A/N feedback for it may receive the same LBT typeindication through the PDSCH (e.g., the header part of MAC CE) of Msg.B, and may perform channel access procedure using the indicated LBT type(e.g., Cat-2 LBT).

If the base station divides the UE into N (e.g., N=2) groups through aspecific criterion, and indicates different LBT types to the N (e.g.,N=2) groups for a specific reason (e.g., whether the base stationsuccessfully received Msg B), the LBT type corresponding to each groupis used. UEs belonging to a specific group may perform a channel accessprocedure using the same LBT type.

Different LBT types may be indicated using an independent MAC CE headerfield and the like. If the base station indicates the LBT type for onegroup through a specific MAC CE header field, the LBT type of anothergroup may be determined as an LBT type promised in advance according tothe indicated MAC CE header field.

3-1-C. Opt 3) the base station indicates the LBT type common to all UEs(or group of UE) through higher layer signaling (e.g., SIB or RMSI,etc.)

If configured as 3-1-C, among the UEs receiving Msg. B, the UE thatneeds to transmit A/N feedback for it may receive the same LBT typeindication through higher layer signaling (e.g., SIB or RMSI) andperform channel access procedure using the indicated LBT type (e.g.,Cat-2 LBT).

If the base station divides the UE into N (e.g., N=2) groups through aspecific criterion and indicates different LBT types to the N(e.g., N=2)groups for a specific reason, the LBT type corresponding to each groupis used. UEs belonging to a specific group may perform a channel accessprocedure using the same LBT type.

Different LBT types may be indicated through independent higher layersignaling and the like. If the base station indicates the LBT type forone group through higher layer signaling, the LBT type of the othergroup may be determined as an LBT type promised in advance according tothe indicated higher layer signaling.

3-1-D. When the base station commonly indicates the LBT type, resourceoverhead for indicating may be reduced, and there is an advantage thatit may be easy to multiplex the A/N to be transmitted by the UE.However, when A/N multiplexing is not performed, since the UEsperforming the common LBT type can simultaneously perform channelaccess, the probability of collision between A/N transmissionsincreases.

3-2. Method of receiving an indication of a UE-specific LBT type foreach success-RAR to the UE receiving Msg. B

3-2-A. Indicate the UE-specific LBT type for each success-RAR, by addinga specific field (or using a reserved field) to a portion indicating avalue according to each preamble (and/or PUSCH) transmission of the MACCE included in the PDSCH carrying Msg B,

If configured in this way, among the UEs receiving Msg. B, the UE thatneeds to transmit A/N feedback for it may receive an indication of theUE-specific LBT type for each success-RAR through the MAC CE, and mayperform a channel access using the indicated LBT type. Accordingly, theUE transmits A/N feedback based on the indicated LBT type.

When the base station indicates a UE-specific LBT type for each successRAR, since the time for performing a channel access between the UEs mayvary, the probability of collision between A/N transmission is reduced.However, there are disadvantages in that a resource overhead forspecifically indicating a UE occurs and it is difficult to perform A/Nmultiplexing.

3-3. Method of indicating the LBT type to the UE receiving Msg. B indifferent ways depending on whether the base station has successfullyreceived Msg. B.

For example, the base station may indicate common LBT type throughsuccess-RAR and may indicate the RAPID-specific LBT type of the MAC-CE(in the RAR message) through the fallback RAR.

Here, each option of 3-1 in embodiment 3 may be applied as a method ofindicating the common LBT type.

3.4 EMBODIMENT 4 RA Field Configuration of 4-Step Msg. 2 RAR or 2-StepFall-Back RAR and LBT Type Indication Method for Msg 3 PUSCHTransmission

Msg. 2 RAR of the conventional 4-step RACH procedure is defined as shownin FIG. 15.

In addition, 27 bits constituting the UL grant of the Msg. 2 RAR aredefined as shown in table 3-4.

TABLE 15 RAR grant field Number of bits Frequency hopping flag 1 PUSCHfrequency resource allocation 14 PUSCH time resource allocation 4 MCS 4TPC command for PUSCH 3 CSI request 1

Additionally, the CSI request field (CSI request field) may be used orreserved depending on whether the contention is as follows. (“In anon-contention based random access procedure, the CSI request field inthe RAR UL grant indicates whether or not the UE includes an aperiodicCSI report in the corresponding PUSCH transmission according to [6, TS38.214]. In a contention based random access procedure, the CSI requestfield is reserved.”)

Since the LBT type of Msg. 3 PUSCH needs to be transmitted through theRAR, the following methods may be proposed.

Proposed method 4-1-1: Method of indicating the LBT type using thereserved 1 bit of RAR.

When using 1 bit to indicate the LBT type, 1 bit may indicate eitherCat-2 LBT or Cat-4 LBT.

Proposed method 4-1-2: Since the CSI request field of the RAR UL grantis reserved in the contention-based RACH process, a method forindicating the LBT type using 1 bit of the CSI request field may beproposed.

When indicating the LBT type using 1 bit of the CSI request field, 1 bitof the CSI request field may indicate either Cat-2 LBT or Cat-4 LBT.

However, in the non-contention-based RACH procedure (e.g., contentionfree RACH), since the CSI request field is used, another proposed methodmay be used.

Proposed method 4-1-3: Method of indicating the LBT type using a fieldunnecessary in the shared spectrum operation among RAR UL grants.

For example, when the frequency resource for Msg 3 PUSCH transmission isallocated in an interlace structure during NR-U operation, since thefrequency hopping flag field does not need to be used, the LBT type maybe indicated by using (reinterpreting) 1 bit of the frequency hoppingflag field.

In the case of indicating the LBT type using 1 bit of the frequencyhopping flag field, 1 bit of the frequency hopping flag field mayindicate either Cat-2 LBT or Cat-4 LBT.

Even when the frequency resource for Msg. 3 PUSCH transmission duringshared spectrum operation is indicated by contiguous PRB allocation ofthe conventional system, the LBT type may be indicated through thefrequency hopping flag field, but since frequency hopping is required incontiguous PRB allocation, the frequency hopping flag field may be usedfor its intended purpose.

Proposed method 4-1-4: Method of indicating the LBT type using the MSB(Most Significant Bit) (or LSB; Least Significant Bit) L bit(s) of aspecific field.

For example, in the PUSCH frequency resource allocation field, thenumber of bits used as shown in Table 16 varies according to theresource allocation type. Table 16 shows the number of bits of thefrequency resource allocation field for PUSCH transmission based on the20 MHz LBT subband.

TABLE 16 Rel-15 RA Type 0 (bit map) Configuration 1 Configuration 2Rel-16 (Smaller RBG (Larger RBG RA Type 1 Interlace level SCS Size)Size) (RIV) allocation 15 kHz 14 (RBG size 8) 7 (RBG size 16) 13 Alt1)10 (Bit map) (106 PRBs) Alt2) 6 (RIV) 30 kHz 13 (RBG size 4) 7 (RBG size8)  11 5 (Bit map) (51 PRBs) 15 kHz 12 (RBG size 8) 6 (RBG size 16) 13Alt1) 10 (Bit map) (96 PRBs) Alt2) 6 (RIV) 30 kHz 12 (RBG size 4) 6 (RBGsize 8)  11 5 (Bit map) (48 PRBs)

Referring to Table 16, PUSCH frequency resource allocation field may beused from a maximum of 14 bits to a minimum of 5 bits.

Here, the LBT type may be indicated using MSB (or LSB) L bits(s) of thePUSCH frequency resource allocation field.

For example, when the LBT type is indicated using the MSB 1 bit of thePUSCH frequency resource allocation field, the MSB 1 bit of the PUSCHfrequency resource allocation field may indicate Cat-2 LBT or Cat-4 LBT.

As another example, when the LBT type is indicated using 2 bits of theMSB (or LSB) of the PUSCH frequency resource allocation field, two typesof priority classes together with Cat-2 LBT or Cat-4 LBT (e.g., PC0 orPC1) may be indicated.

As another example, when the LBT type is indicated using 3 bits of theMSB (or LSB) of the PUSCH frequency resource allocation field, fourtypes of priority classes (e.g., one of PC0 to PC3) may be indicatedtogether with Cat-2 LBT or Cat-4 LBT. Alternatively, Cat-1 LBT, Cat-2LBT, Cat-4 LBT and various priority classes may be combined andindicated.

Characteristically, the UE interpreting the actual PUSCH frequencyresource allocation field may be configured to understand PUSCHfrequency resource allocation, assuming that the MSB (or LSB) L bitvalue used for the LBT type is 0.

Proposed method 4-1-5: Method of reducing the size of a specific fieldby L bits and making it a field indicating the LBT type by using thereduced L bits.

4-1-5-A: During the RACH process in the shared spectrum, since the Msg 3PUSCH uses the conventional RA type 1 (Rel-15 RA Type 1 in Table 15) ora new RA type (Rel-16 Interlace level allocation in Table 15), the PUSCHfrequency resource allocation field may be configured to 13 bits. Amongthe 14 bits for the conventional PUSCH frequency resource allocationfield, the remaining 1 bit may be configured as a field indicating theLBT type. As an example, when the LBT type is indicated using 1 bit MSBin the 14-bit PUSCH frequency resource allocation field, Cat-2 LBT orCat-4 LBT may be indicated.

4-1-5-B: Additionally, the actual PUSCH frequency resource allocationfield may be configured to a less than 13 bits(e.g., 12 bit, etc.). Theremaining bits among 14 bits for the conventional PUSCH frequencyresource allocation field may be configured as a field indicating theLBT type. As an example, when the LBT type is indicated using 2 bits ofthe MSB (or LSB) in the 14-bit PUSCH frequency resource allocationfield, two types of priority classes (e.g., PC0 or PC1) may be indicatedtogether with Cat-2 LBT or Cat-4 LBT. The UE may be configured tounderstand PUSCH frequency resource allocation assuming that the reducedMSB (or LSB) is 0. For example, among the 14 bits in which theconventional PUSCH frequency resource allocation field is located in theRAR grant, 2 bits of MSB are used as a field indicating a channel accesstype, and 12 bits of LSB are used as a frequency resource allocationfield as in the prior art, but LSB 12 Bits may be interpreted like a14-bit field, assuming that there are zeros of two bits before 12 bits.As another example, when PUSCH frequency resource allocation isperformed with 12 bits, the UE assumes that 1-bit MSB (or LSB) is 0, andmay be configured to understand PUSCH frequency resource allocation.Because RIV requires up to 13 bits, only 13-12=1 bit MSB (or LSB) istreated as 0.

The proposed method 4-1-3 is additionally applied to the proposed method4-1-5, and the LBT type field and the MSB (or LSB) L-bit combination ofthe specific field (e.g., PUSCH frequency resource allocation field) LBTThe type may be indicated.

Proposed method 4-1-6: a combination of the proposed methods of 4-1-1 to4-1-5 may be considered.

That is, the LBT type may be indicated by a combination of reserved 1bit of RAR, and/or CSI request field 1 bit of RAR UL grant, and/or afield not used in a shared spectrum among RAR UL grants, and/or MSB (orLSB) L bit(s) of a specific field.

Additionally, it may be considered that Msg. 3 does not indicate the LBTtype for PUSCH transmission. As an example, when the LBT type for Msg. 3PUSCH transmission is configured to LBE (load based equipment) throughSIB, a default value may be configured/defined as Cat-4 LBT. When theLBT type for Msg. 3 PUSCH transmission is configured to FBE (frame basedequipment) through SIB, the default value may be configured/defined asCat-2 LBT with 25 usec (or with 16 usec).

Characteristically, when the UE is configured to LBE through SIB in the2-step RACH procedure, even if the default value of Msg. A PUSCH (orMsg. 3 PUSCH) transmission is configured/defined as Cat-4 LBT, anothercategory of LBT may be used according to the interval between RO-POs asin the embodiments of the present specification. Similarly, when the UEis configured to FBE through SIB, even if the default value of Msg. APUSCH (or Msg. 3 PUSCH) transmission is configured/defined as Cat-2 LBTwith 25 usec, (in the gap between RO-PO Depending) Cat-2 LBT with 16usec or Cat-1 LBT may be used.

Additionally, not only the LBT type but also the Msg. 3 PUSCH startposition may be additionally signaled through the RAR. This issummarized as follows.

4-2-1) when the legacy NR waveform is configured to (Msg. 3) PUSCHwaveform from the base station,

Opt 1: Applying a fixed starting position to the fixed LBT type for Msg.3 PUSCH transmission

Opt 2: Applying the fixed LBT type to Msg. 3 PUSCH transmission andindicating one of a pluarlity of starting positions to as RAR (or ULgrant of RAR).

Opt 3: Applying the fixed starting position to Msg. 3 PUSCH transmissionand indicating one of a pluarlity of LBT types as RAR (or UL grant ofRAR).

4-2-2) When the interlace waveform is configured as the (Msg. 3) PUSCHwaveform from the base station,

Opt 1: One of a combination of multiple LBT types and multiple startingpositions is indicated by RAR (or UL grant of RAR)

Accordingly, the LBT type indicated through the RAR grant in theprevious proposed methods (suggested methods 4-1-1 to 4-1-6, etc.) maymean a combination of LBT type or starting position or {LBT type,starting position} according to Opt 1 to 3 method of 4-2-1. At thistime, assuming that the starting symbol of the resource mapping thePUSCH signal is indicated by Symbol #K, when the starting position isindicated by 1-bit, one of {Symbol #K, Symbol#(K−N)+25 us} may beindicated, or one of {Symbol #K, Symbol#(K−N)+25 us +TA} may beindicated. On the other hand, if the starting position is not indicatedthrough the RAR grant and is determined as a single fixed value, thevalue may be defined as Symbol #K.

As described above through the proposed method 4-1-5-B, when it isnecessary to indicate the LBT type for Msg 3 transmission from the basestation (e.g., for operation with shared spectrum channel access), thesize of the PUSCH frequency resource allocation field of the RAR may bereduced by 2 bits. 2 bits not used as the PUSCH frequency resourceallocation field may be used as a field for explicitly transmitting theLBT type. A field for transmitting the LBT type may be defined as aChannelAccess-CPext field. The fields of the RAR grant shown in Table 16may be redefined as shown in Table 17.

TABLE 17 RAR grant field Number of bits Frequency hopping flag 1 PUSCHfrequency resource 14, for operation without shared spectrum allocationchannel access 12, for operation with shared spectrum channel accessPUSCH time resource 4 allocation MCS 4 TPC command for PUSCH 3 CSIrequest 1 ChannelAccess-CPext 0, for operation without shared spectrumchannel access 2, for operation with shared spectrum channel access

On the other hand, when the size (i.e., N_(BWP) ^(size)) of the PUSCHresource allocation field becomes 12 (i.e., when it is necessary toindicate the LBT type for Msg 3 transmission from the base station), thecontents of Table 18 below describing truncation and padding of theconventional PUSCH frequency resource allocation field may beinsufficient for the UE to interpret the ChannelAccess-CPext field andthe PUSCH frequency resource allocation field.

TABLE 18  The frequency domain resource allocation is by uplink resourceallocation type 1 if useInterlacePUSCH-Common is not provided and byuplink resource allocation type 2 if useInterlacePUSCH-Common isprovided [6, TS 38.214]. For an initial UL BWP size of N_(BWP) ^(size)RBs, a UE processes the frequency domain resource assignment field asfollows    - if N_(BWP) ^(size)≤180     -truncate the frequency domainresource assignment field to its   ┌log₂(N_(BWP) ^(size) * (N_(BWP)^(size) + 1)/2)┐ least significant bits and interpret the truncated  frequency resource assignment field as for the frequency resourceassignment field in   DCI format 0_0 as described in [5, TS 38.212]   - else     -insert ┌log₂(N_(BWP) ^(size) * (N_(BWP) ^(size) + 1)/2)┐− 14 most significant bits with value set   to ‘0’ after the N_(UL, hop)bits to the frequency domain resource assignment field, where  N_(UL, hop) = 0 if the frequency hopping flag is set to ‘0’ andN_(UL, hop) is provided in Table   8.3-1 if the hopping flag bit is setto ‘1’, and interpret the expanded frequency resource   assignment fieldas for the frequency resource assignment field in DCI format 0_0 as  described in [5, TS 38.212]    - end if

Therefore, Table 18 may be modified based on the proposal of the presentdisclosure as follows.

4-3-1. For the operation without shared spectrum channel access,operation of conventional system.

4-3-1-A. If the number of PRBs in BWP is 180 or less,

the UE truncates as much as the LSB┌log₂(N_(BWP) ^(size)**N_(BWP)^(size)+1)/2)┐ of the FDRA (Frequency domain resource assignment) field,and interprets the truncated FDRA field as an FDRA field of DCI format0_0.

4-3-1-B. If the number of PRBs in BWP is more than 180,

the UE performs padding 0 as much as MSB┌log₂(N_(BWP) ^(size)*(N_(BWP)^(size)1)/2)┐−14 in front of the FDRA field, and interprets the extendedFERA field as an FDRA field of DCI format 0_0. At this time, if thefrequency hopping flag is 0, NUL,hop is 0, and if the frequency hoppingflag is 1, NUL,hop follows Table 19.

TABLE 19 Number of PRBs in Value of N_(UL, hop) Frequency offset initialactive UL BWP Hopping Bits for 2^(nd) hop N_(BWP) ^(size) < 50 0└N_(BWP) ^(size)/2┘ 1 └N_(BWP) ^(size)/4┘ N_(BWP) ^(size) ≥ 50 00└N_(BWP) ^(size)/2┘ 01 └N_(BWP) ^(size)/4┘ 10 −└N_(BWP) ^(size)/4┘  11Reserved

4-3-1-B. End If

4-3-2. For the operation with shared spectrum channel access

4-3-2-A. When the higher layer parameter useInterlacePUSCH-Common is notprovided (If useInterlacePUSCH-Common is not provided), that is, whencontinuous mapping which is uplink resource allocation type 1 (uplinkresource allocation type 1) is used,

4-3-2-A-i. If the number of PRBs (N_(BWP) ^(size)) in BWP is 90 or less

the UE truncates as much as the LSB(┌log₂(N_(BWP) ^(size)*(N_(BWP)^(size)+1)/2┐ of the FDRA field, and interprets the truncated FDRA fieldas an FDRA field of DCI format 0_0.

4-3-2-A-ii. If the number of PRBs in BWP is more than 90,

the UE performs padding 0 as much as MSB in front of the FDRA field, andinterprets the extended FDRA field as an FDRA field of DCI format 0_0.At this time, if the frequency hopping flag is 0, NUL,hop is 0, and ifthe frequency hopping flag is 1, NUL,hop follows Table 19.

4-3-2-A-iii. End If

4-3-2-A-iv. In this case, the new threshold value of 90 means themaximum number of PRBs of the BWP that can be transmitted in 12 bitswhen the uplink resource allocation type 1 (MV) scheme is used.(90*91/2=4095≤4096=212)

4-3-2-B. If higher layer parameter useInterlacePUSCH-Common is provided,that is, when the uplink resource allocation type 2 which is interlacemapping is used

4-3-2-B-i. the UE truncates LSB (or MSB) X bits of the FDRA field, andinterprets the truncated FDRA field as the FDRA field of DCI format 0_0.When PUSCH is transmitted in a band in which 30 kHz SCS is configured(i.e., μ=1), X is 5, and when PUSCH is transmitted in a band in which 15kHz SCS is configured (i.e., μ=0), X is 6.

4-3-2-B-ii. When LBT sub-band allocation is added, the Y bit may beadded in front of or rear of the X bit of FDRA field. According to thenumber of LBT subbands set in the BWP, Y may be determined as one of {0,1, 2, 3, 4}.

Based on 4-3-1 and 4-3-2, table 18 may be modified as shown in table 20.

TABLE 20  The frequency domain resource allocation is by uplink resourceallocation type 1 if useInterlacePUSCH-Common is not provided and byuplink resource allocation type 2 if useInterlacePUSCH-Common isprovided [6, TS 38.214], For an initial UL BWP size of N_(BWP) ^(size)RBs, a UE processes the frequency domain resource assignment field forthe operation without shared spectrum channel access as follows   - ifN_(BWP) ^(size)≤180 - truncate the frequency domain resource assignmentfield to its ┌log₂(N_(BWP) ^(size) * (N_(BWP) ^(size) + 1)/2)┐ leastsignificant bits and interpret the truncated frequency resourceassignment field as for the frequency resource assignment field in DCIformat 0_0 as described in [5, TS 38.212]   - else - insert┌log₂(N_(BWP) ^(size) * (N_(BWP) ^(size) + 1)/2)┐ − 14 most significantbits with value set to ‘0’ after the N_(UL, hop) bits to the frequencydomain resource assignment field, where N_(UL, hop) = 0 if the frequencyhopping flag is set to ‘0’ and N_(UL, hop) is provided in Table 8.3-1 ifthe hopping flag bit is set to ‘1’, and interpret the expanded frequencyresource assignment field as for the frequency resource assignment fieldin DCI format 0_0 as described in [5, TS 38.212]   - end if For aninitial UL BWP size of N_(BWP) ^(size) RBs, a UE processes the frequencydomain resource assignment field for the operation with shared spectrumchannel access as follows   - if the higher layer parameteruseInterlacePUSCH-Common-r16 is not configured - if N_(BWP) ^(size)≤90  - truncate the frequency domain resource assignment field to its┌log2(N_(BWP) ^(size) * (N_(BWP) ^(size) + 1)/2)┐ least significant bitsand interpret the truncated frequency resource assignment field as forthe frequency resource assignment field in DCI format 0_0 as describedin [5, TS 38.212] - else   - insert ┌log2(N_(BWP) ^(size) * (N_(BWP)^(size) + 1)/2)┐ − 12 most significant bits with value set to ‘0’ afterthe N_(UL, hop) bits to the frequency domain resource assignment field,where N_(UL, hop) = 0 if the frequency hopping flag is set to ‘0’ andN_(UL, hop) is provided in Table 8.3-1 if the hopping flag bit is set to‘1’, and interpret the expanded frequency resource assignment field asfor the frequency resource assignment field in DCI format 0_0 asdescribed in [5, TS 38.212] - end if   - else if the higher layerparameter useInterlacePUSCH-Common-r16 is configured - if the subcarrierspacing for the PUSCH transmission is 30 kHz   - truncate the frequencydomain resource assignment field to its 5 least significant bits andinterpret the truncated frequency resource assignment field as for thefrequency resource assignment field in DCI format 0_0 as described in[5, TS 38.212] - else if the subcarrier spacing for the PUSCHtransmission is 15 kHz   - truncate the frequency domain resourceassignment field to its 6 least significant bits and interpret thetruncated frequency resource assignment field as for the frequencyresource assignment field in DCI format 0_0 as described in [5, TS38.212]  - end if

Additionally, when useInterlacePUSCH-Common is provided, the RAR ULgrant field size may be defined/configured as follows.

4-4-1. Alt 1)

Since only X bits are required for the actual FDRA, the FDRA field sizeis defined as X bits and the remaining bits may be used as a reservedfield. In addition, the reserved field position may be immediately infront of or rear of the FDRA field, or a specific position of the RAR ULgrant (e.g., the last, i.e., LSBs in RAR UL grant).

Characteristically, when the SCS for PUSCH transmission is 30 kHz, X maybe 5 bits, and when the SCS for PUSCH transmission is 35 kHz, X may be 6bits.

As an example, if the example in which the reserved field position isthe last one is applied, each field in the RAR grant may be defined asshown in Table 21.

TABLE 21 RAR grant field Number of bits Frequency hopping flag 1(reserved) PUSCH frequency resource 5, if the subcarrier spacing for thePUSCH transmission allocation is 30 kHz 6, if the subcarrier spacing forthe PUSCH transmission is 15 kHz PUSCH time resource 4 allocation MCS 4TPC command for PUSCH 3 CSI request 1 ChannelAccess-CPext 0, foroperation without shared spectrum channel access 2, for operation withshared spectrum channel access Reserved 6, if the subcarrier spacing forthe PUSCH transmission is 15 kHz and for operation with shared spectrumchannel access 7, if the subcarrier spacing for the PUSCH transmissionis 30 kHz and for operation with shared spectrum channel access or, 6,if the subcarrier spacing for the PUSCH transmission is 15 kHz and foroperation with shared spectrum channel access 7, if the subcarrierspacing for the PUSCH transmission is 30 kHz and for operation withshared spectrum channel access 8, if the subcarrier spacing for thePUSCH transmission is 15 kHz and for operation without shared spectrumchannel access 9, if the subcarrier spacing for the PUSCH transmissionis 30 kHz and for operation without shared spectrum channel access

4-4-2. Alt 2)

Since only X bits are required for the actual FDRA, the FDRA field sizemay be defined as X bits and the remaining bits may be used as areserved field. In addition, the reserved field position may beimmediately in front of or rear of the FDRA field, or a specificposition of the RAR UL grant (e.g., the last, i.e., LSBs in RAR ULgrant).

At this time, since 5 bits are required when the SCS for PUSCHtransmission is 30 kHz and 6 bits are required when the SCS is 15 kHz, Xmay be configured to 6 bits to satisfy both SCSs.

In this case, when the SCS is 30 kHz, the UE may truncate 5 bits of theLSB (or MSB) of the FDRA field and interpret it as the FDRA field.

As an example, if the example in which the reserved field position isthe last one is applied, each field in the RAR grant may be defined asshown in Table 22.

TABLE 22 RAR grant field Number of bits Frequency hopping flag 1(reserved) PUSCH frequency resource 6 allocation PUSCH time resource 4allocation MCS 4 TPC command for PUSCH 3 CSI request 1ChannelAccess-CPext 0, for operation without shared spectrum channelaccess 2, for operation with shared spectrum channel access Reserved 6,for operation with shared spectrum channel access or 6, for operationwith shared spectrum channel access 8, for operation without sharedspectrum channel access

Y bit for LBT subband allocation may be further included in PUSCHfrequency resource allocation. Accordingly, in Table 21 and/or Table 22,the Y bit may be added to the PUSCH frequency resource allocation fieldand the Y bit may be omitted from the Reserved field.

Network Access and Communication Procedure

A UE may perform network access procedure to perform the methods and/orprocedures proposed/described above. For example, the UE may receive andstore configuration information and system information necessary toperform methods and/or procedures described/proposed above in a memorywhile performing access to network (e.g., a base station). Configurationinformation necessary for the present disclosure may be received throughhigher layer(e.g., RRC layer, Medium Access Control, MAC, layer etc.)signaling.

FIG. 16 illustrates an initial network connection and a communicationprocess thereafter. In NR, a physical channel, a reference signal, maybe transmitted using beam-forming. When beam-forming-based signaltransmission is supported, a beam management process may be involved inorder to align beams between the base station and the UE. In addition,the signal proposed in the present disclosure may betransmitted/received using beam-forming. In Radio Resource Control (RRC)IDLE mode, beam alignment may be performed based on SSB. On the otherhand, in the RRC CONNECTED mode, beam alignment may be performed basedon CSI-RS (in DL) and SRS (in UL). Meanwhile, when beam-forming-basedsignal transmission is not supported, an operation related to a beam maybe omitted in the following description.

Referring to FIG. 16, the base station (e.g., BS) may transmit SSBperiodically (S702). Here, the SSB includes PSS/SSS/PBCH. The SSB may betransmitted using beam sweeping. Thereafter, the base station maytransmit Remaining Minimum System Information (RMSI) and Other SystemInformation (OSI) (S704). The RMSI may include information (e.g., PRACHconfiguration information) necessary for the UE to initially access thebase station. Meanwhile, the UE identifies the best SSB after performingSSB detection. Thereafter, the UE may transmit the RACH preamble(Message 1, Msg1) to the base station by using the PRACH resourcelinked/corresponding to the index (i.e., beam) of the best SSB (S706).The beam direction of the RACH preamble is related to the PRACHresource. Association between the PRACH resource (and/or the RACHpreamble) and the SSB (index) may be configured through systeminformation (e.g., RMSI). Thereafter, as part of the RACH process, thebase station transmits a random access response (RAR) (Msg2) in responseto the RACH preamble (S708), and the UE transmits Msg3 (e.g., RRCConnection Request) using the UL grant in the RAR. After transmitting(S710), the base station may transmit a contention resolution message(Msg4) (S720). Msg4 may include RRC Connection Setup.

When the RRC connection is established between the base station and theUE through the RACH procedure, subsequent beam alignment may beperformed based on SSB/CSI-RS (in DL) and SRS (in UL). For example, theUE may receive SSB/CSI-RS (S714). The SSB/CSI-RS may be used by the UEto generate a beam/CSI report. Meanwhile, the base station may request abeam/CSI report from the terminal through DCI (S716). In this case, theUE may generate a beam/CSI report based on SSB/CSI-RS and transmit thegenerated beam/CSI report to the base station through PUSCH/PUCCH(S718). The beam/CSI report may include a beam measurement result,information about a preferred beam, and the like. The base station andthe UE may switch beams based on the beam/CSI report (S720 a, S720 b).

Thereafter, the UE and the base station may perform theabove-described/proposed procedures and/or methods. For example, the UEand the base station, based on configuration information obtained in thenetwork access procedure (e.g., system information acquisitionprocedure, RRC connection procedure through the RACH etc.), may processthe information in the memory to transmit the radio signal, or processthe received radio signal and store it in the memory according to theproposal of the present disclosure. Here, the radio signal may includeat least one of PDCCH, PDSCH, and RS (Reference Signal) for downlink,and may include at least one of PUCCH, PUSCH, and SRS for uplink.

Implementation Example

FIG. 17 is a flowchart of a signal transmission/reception methodaccording to embodiments of the present disclosure.

Referring to FIG. 17, embodiments of the present disclosure may beperformed by the UE and may include a step of receiving RAR based on aPRACH (S1701) and a step of transmitting a PUSCH based on RAR. Althoughnot shown, the embodiment of the present disclosure performed from thestandpoint of the base station may include a step of transmitting RARbased on PRACH and receiving a PUSCH based on RAR.

RAR may be configured based on the embodiment 4. For example, the RARmay be a fallback RAR for message A in a 2-step random access procedure.RAR may be Msg. 2 RAR for Msg. 1 PRACH in a 4-step random accessprocedure.

The channel access type (LBT type) for PUSCH (Msg. 3 PUSCH) may bedetermined based on one or more of the methods of the proposed method4-1-1 to 4-1-6 of the embodiment 4.

For example, the channel access type for the PUSCH may be determinedbased on the proposed method 4-1-5 of the fourth embodiment. Accordingto the proposed method 4-1-5, the channel access type for the PUSCH forthe shared spectrum channel access may be determined based on a specificfield of the RAR grant in the RAR. In other words, a specific field ofthe RAR grant included in the RAR in the PDSCH may indicate the channelaccess type.

A specific field may be used as a PUSCH frequency resource allocationfield for a non-shared spectrum. In other words, some of the bits usedas the PUSCH frequency resource allocation field in the non-sharedspectrum may be used as a specific field for indicating a channel accesstype in the shared spectrum. In the non-shared spectrum, the PUSCHfrequency resource allocation field consists of 14 bits, of which 2 bitsare used for a specific field in the shared spectrum. 12 bits except for2 bits used for a specific field are used for the PUSCH frequencyresource allocation field in the shared spectrum.

The 12-bit PUSCH frequency resource allocation field may be interpretedas 12 bits, based on the size of the BWP, or MSBs whose value is set to0 may be added and interpreted. For example, the UE may interpret theshared spectrum by adding 2 bits of MSB set to 0 to 12 bits of the PUSCHfrequency resource allocation field.

RAR is UE-specifically transmitted and received between the UE and thebase station. Therefore, the channel access type by the specific fieldis also indicated as UE-specific.

The UE performs a channel access procedure for PUSCH transmission basedon the channel access type indicated by a specific field.

The name of the specific field may be a ChannelAccess-CPext field.

In addition to the operation described with reference to FIG. 17, one ormore of the operations described with reference to FIGS. 1 to 16 and/orthe operations described with respect to embodiments 1 to 4 may becombined and additionally performed. For example, the UE may performuplink LBT before transmission of the PRACH. Alternatively, the UE mayselect the SSB before transmission of the PRACH.

Example of a Communication System to which the Present Disclosure isApplied

Although not limited thereto, various descriptions, functions,procedures, proposals, methods, and/or operational flowcharts of thepresent disclosure disclosed in this document may be applied in variousfields requiring wireless communication/connection (e.g., 5G) betweendevices.

Hereinafter, it will be exemplified in more detail with reference to thedrawings. In the following drawings/descriptions, the same referencenumerals may represent the same or corresponding hardware blocks,software blocks, or functional blocks, unless otherwise indicated.

FIG. 18 illustrates a communication system 1 applied to the presentdisclosure.

Referring to FIG. 18, the communication system 1 applied to the presentdisclosure includes a wireless device, a base station, and a network.Here, the wireless device means a device that performs communicationusing a wireless access technology (e.g., 5G NR (New RAT), LTE (LongTerm Evolution)), and may be referred to as a communication/wireless/5Gdevice. Although not limited thereto, the wireless device includes arobot 100 a, a vehicle 100 b-1, 100 b-2, an eXtended Reality (XR) device100 c, a hand-held device 100 d, and a home appliance 100 e, an Internetof Thing (IoT) device 100 f, and an AI device/server 400. For example,the vehicle may include a vehicle equipped with a wireless communicationfunction, an autonomous driving vehicle, a vehicle capable of performinginter-vehicle communication, and the like. Here, the vehicle may includean Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR(Augmented Reality)/VR (Virtual Reality)/MR (Mixed Reality) devices, andmay be implemented in the form of a Head-Mounted Device (HMD), a Head-UpDisplay (HUD) provided in a vehicle, a television, a smartphone, acomputer, a wearable device, a home appliance, a digital signage, avehicle, a robot, and the like. The portable device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smartglasses), a computer (e.g., a laptop computer), and the like. Homeappliances may include a TV, a refrigerator, a washing machine, and thelike. The IoT device may include a sensor, a smart meter, and the like.For example, the base station and the network may be implemented as awireless device, and the specific wireless device 200 a may operate as abase station/network node to other wireless devices.

The wireless devices 100 a to 100 f may be connected to the network 300through the base station 200. Artificial intelligence (AI) technologymay be applied to the wireless devices 100 a to 100 f, and the wirelessdevices 100 a to 100 f may be connected to the AI server 400 through thenetwork 300. The network 300 may be configured using a 3G network, a 4G(e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices100 a to 100 f may communicate with each other through the base station200/network 300, but may also communicate directly (e.g., sidelinkcommunication) without passing through the base station/network. Forexample, the vehicles 100 b-1 and 100 b-2 may perform directcommunication (e.g., Vehicle to Vehicle (V2V)/Vehicle to everything(V2X) communication). In addition, the IoT device (e.g., sensor) maydirectly communicate with other IoT devices (e.g., sensor) or otherwireless devices 100 a to 100 f.

Wireless communication/connection 150 a, 150 b, 150 c may be performedbetween the wireless devices 100 a to 100 f and the base station 200 andbetween the base station 200 and the base station 200. Here, wirelesscommunication/connection may be made through various wireless accesstechnologies (e.g., 5G NR) such as uplink/downlink communication 150 a,sidelink communication 150 b (or D2D communication), and inter-basestation communication 150 c. Through the wirelesscommunication/connection 150 a, 150 b, and 150 c, the wireless deviceand the base station/wireless device, and the base station and the basestation may transmit/receive radio signals to each other. For example,the wireless communication/connection 150 a, 150 b, and 150 c maytransmit/receive signals through various physical channels. To this end,based on various proposals of the present disclosure, at least part ofvarious configuration information configuration processes, varioussignal processing processes (e.g., channel encoding/decoding,modulation/demodulation, resource mapping/demapping, etc.), resourceallocation processes, etc. may be performed.

Example of a Wireless Device to which the Present Disclosure is Applied

FIG. 19 illustrates wireless devices to which the present disclosure isapplied.

Referring to FIG. 19, the first wireless device 100 and the secondwireless device 200 may transmit/receive wireless signals throughvarious wireless access technologies (e.g., LTE, NR). Here, {firstwireless device 100, second wireless device 200} may correspond to{wireless device 100 x, base station 200} and/or {wireless device 100 x,wireless device 100 x} of FIG. 18.

The first wireless device 100 includes one or more processors 102 andone or more memories 104, and may further include one or moretransceivers 106 and/or one or more antennas 108. The processor 102controls the memory 104 and/or the transceiver 106 and may be configuredto implement the descriptions, functions, procedures, suggestions,methods, and/or operational flow charts disclosed herein. For example,the processor 102 may process information in the memory 104 to generatefirst information/signal, and then transmit a wireless signal includingthe first information/signal through the transceiver 106. In addition,the processor 102 may receive the radio signal including the secondinformation/signal through the transceiver 106, and then store theinformation obtained from the signal processing of the secondinformation/signal in the memory 104. The memory 104 may be connected tothe processor 102 and may store various information related to theoperation of the processor 102. For example, the memory 104 may storesoftware code including instructions for performing some or all ofprocesses controlled by the processor 102, or for performing thedescriptions, functions, procedures, suggestions, methods, and/oroperational flowcharts disclosed in the document. Here, the processor102 and the memory 104 may be part of a communication modem/circuit/chipdesigned to implement a wireless communication technology (e.g., LTE,NR). A transceiver 106 may be coupled to the processor 102 and maytransmit and/or receive wireless signals via one or more antennas 108.The transceiver 106 may include a transmitter and/or a receiver. Thetransceiver 106 may be used interchangeably with a radio frequency (RF)unit. In the present disclosure, a wireless device may refer to acommunication modem/circuit/chip.

The second wireless device 200 includes one or more processors 202, oneor more memories 204, and may further include one or more transceivers206 and/or one or more antennas 208. The processor 202 controls thememory 204 and/or the transceiver 206 and may be configured to implementthe descriptions, functions, procedures, suggestions, methods, and/orflow charts disclosed herein. For example, the processor 202 may processthe information in the memory 204 to generate third information/signal,and then transmit a wireless signal including the thirdinformation/signal through the transceiver 206. In addition, theprocessor 202 may receive the radio signal including the fourthinformation/signal through the transceiver 206, and then storeinformation obtained from signal processing of the fourthinformation/signal in the memory 204. The memory 204 may be connected tothe processor 202 and may store various information related to theoperation of the processor 202. For example, the memory 204 may storesoftware code including instructions for performing some or all of theprocesses controlled by the processor 202, or for performing thedescriptions, functions, procedures, suggestions, methods, and/oroperational flowcharts disclosed in the document. Here, the processor202 and the memory 204 may be part of a communication modem/circuit/chipdesigned to implement a wireless communication technology (e.g., LTE,NR). The transceiver 206 may be coupled to the processor 202 and maytransmit and/or receive wireless signals via one or more antennas 208.Transceiver 206 may include a transmitter and/or receiver. Transceiver206 may be used interchangeably with an RF unit. In the presentdisclosure, a wireless device may refer to a communicationmodem/circuit/chip.

Hereinafter, hardware elements of the wireless devices 100 and 200 willbe described in more detail. Although not limited thereto, one or moreprotocol layers may be implemented by one or more processors 102, 202.For example, one or more processors 102, 202 may implement one or morelayers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP).The one or more processors 102, 202 may generate one or more ProtocolData Units (PDUs) and/or one or more Service Data Units (SDUs) accordingto the description, function, procedure, proposal, method and/oroperational flowcharts disclosed herein. One or more processors 102, 202may generate messages, control information, data, or informationaccording to the description, function, procedure, proposal, method,and/or flow charts disclosed herein. The one or more processors 102 and202 generate a signal (e.g., a baseband signal) including PDUs, SDUs,messages, control information, data or information according to thefunctions, procedures, proposals and/or methods disclosed herein andprovide it to one or more transceivers 106 and 206. One or moreprocessors 102, 202 may receive signals (e.g., baseband signals) fromone or more transceivers 106, 206, and may obtain PDUs, SDUs, messages,control information, data, or information according to description,functions, procedures, proposals, methods, and/or operational flowchartsdisclosed herein.

One or more processors 102, 202 may be referred to as a controller,microcontroller, microprocessor, or microcomputer. One or moreprocessors 102, 202 may be implemented by hardware, firmware, software,or a combination thereof. For example, one or more Application SpecificIntegrated Circuits (ASICs), one or more Digital Signal Processors(DSPs), one or more Digital Signal Processing Devices (DSPDs), one ormore Programmable Logic Devices (PLDs), or one or more FieldProgrammable Gate Arrays (FPGAs) may be included in one or moreprocessors 102, 202. The descriptions, functions, procedures,suggestions, methods, and/or flowcharts of operations disclosed in thisdocument may be implemented using firmware or software, and the firmwareor software may be implemented to include modules, procedures,functions, and the like. Firmware or software configured to perform thedescriptions, functions, procedures, suggestions, methods, and/or flowcharts disclosed herein may be included in one or more processors 102,202 or may be stored in one or more memories 104, 204 and driven by oneor more processors 102, 202. The descriptions, functions, procedures,suggestions, methods, and/or flowcharts of operations disclosed hereinmay be implemented using firmware or software in the form of code,instructions, and/or a set of instructions.

One or more memories 104, 204 may be coupled to one or more processors102, 202 and may store various forms of data, signals, messages,information, programs, codes, instructions, and/or instructions. One ormore memories 104, 204 may be comprised of ROM, RAM, EPROM, flashmemory, hard drives, registers, cache memory, computer readable storagemedia, and/or combinations thereof. One or more memories 104, 204 may belocated inside and/or external to one or more processors 102, 202.Additionally, one or more memories 104, 204 may be coupled to one ormore processors 102, 202 through various technologies, such as wired orwireless connections.

One or more transceivers 106, 206 may transmit user data, controlinformation, radio signals/channels, etc. referred to in the methodsand/or operation flowcharts herein, to one or more other devices. Theone or more transceivers 106, 206 may receive user data, controlinformation, radio signals/channels, etc. referred to in thedescriptions, functions, procedures, suggestions, methods and/or flowcharts, etc. disclosed herein, from one or more other devices. Forexample, one or more transceivers 106, 206 may be coupled to one or moreprocessors 102, 202 and may transmit and receive wireless signals. Forexample, one or more processors 102, 202 may control one or moretransceivers 106, 206 to transmit user data, control information, orwireless signals to one or more other devices. In addition, one or moreprocessors 102, 202 may control one or more transceivers 106, 206 toreceive user data, control information, or wireless signals from one ormore other devices. Further, one or more transceivers 106, 206 may becoupled to one or more antennas 108, 208, and may be configured totransmit and receive, through the one or more antennas 108, 208, userdata, control information, radio signals/channels, etc. mentioned indescription, functions, procedures, proposals, methods and/or operationflowcharts. In this document, one or more antennas may be a plurality ofphysical antennas or a plurality of logical antennas (e.g., antennaports). The one or more transceivers 106, 206 convert the received radiosignal/channel, etc. from the RF band signal into a baseband signal toprocess the received user data, control information, radiosignal/channel, etc. using the one or more processors 102, 202. One ormore transceivers 106 and 206 may convert user data, controlinformation, radio signals/channels, etc. processed using one or moreprocessors 102 and 202 from baseband signals to RF band signals. To thisend, one or more transceivers 106, 206 may include (analog) oscillatorsand/or filters.

Example of Application of a Wireless Device to which the PresentDisclosure is Applied

FIG. 20 shows another example of a wireless device applied to thepresent disclosure. The wireless device may be implemented in variousforms according to use-examples/services (refer to FIG. 18).

Referring to FIG. 20, wireless devices 100 and 200 may correspond towireless devices 100 and 200 of FIG. 19, and may consist of variouselements, components, units/units, and/or modules. For example, thewireless devices 100 and 200 may include a communication unit 110, acontrol unit 120, a memory unit 130, and an additional element 140. Thecommunication unit may include communication circuitry 112 andtransceiver(s) 114. For example, communication circuitry 112 may includeone or more processors 102, 202 and/or one or more memories 104, 204 ofFIG. 19. For example, the transceiver(s) 114 may include one or moretransceivers 106, 206 and/or one or more antennas 108, 208 of FIG. 19.The control unit 120 is electrically connected to the communication unit110, the memory unit 130, and the additional element 140, and controlsgeneral operations of the wireless device. For example, the controller120 may control the electrical/mechanical operation of the wirelessdevice based on the program/code/command/information stored in thememory unit 130. In addition, the control unit 120 may transmit theinformation stored in the memory unit 130 to the outside (e.g., anothercommunication device) through the communication unit 110 through awireless/wired interface, or may store information received from theoutside (e.g., another communication device) through a wireless/wiredinterface through the communication unit 110 in the memory unit 130.

The additional element 140 may be variously configured according to thetype of the wireless device. For example, the additional element 140 mayinclude at least one of a power unit/battery, an input/output unit (I/Ounit), a driving unit, and a computing unit. Although not limitedthereto, a wireless device may include a robot (FIGS. 18 and 100 a), avehicle (FIGS. 18, 100 b-1, 100 b-2), an XR device (FIGS. 18 and 100 c),a mobile device (FIGS. 18 and 100 d), and a home appliance (FIG. 18, 100e), IoT device (FIG. 18, 100 f), digital broadcasting terminal, hologramdevice, public safety device, MTC device, medical device, fintech device(or financial device), security device, climate/environment device, Itmay be implemented in the form of an AI server/device (FIGS. 18 and400), a base station (FIGS. 18 and 200), and a network node. Thewireless device may be mobile or used in a fixed location depending onthe use-example/service.

In FIG. 20, various elements, components, units/units, and/or modules inthe wireless devices 100 and 200 may be all interconnected through awired interface, or at least some of them may be wirelessly connectedthrough the communication unit 110. For example, in the wireless devices100 and 200, the control unit 120 and the communication unit 110 areconnected by wire, and the control unit 120 and the first unit (e.g.,130, 140) may be connected to the communication unit 110 wirelesslythrough the communication unit 110. In addition, each element,component, unit/unit, and/or module within the wireless device 100, 200may further include one or more elements. For example, the controller120 may be configured with one or more processor sets. For example, thecontrol unit 120 may be configured as a set of a communication controlprocessor, an application processor, an electronic control unit (ECU), agraphic processing processor, a memory control processor, and the like.As another example, the memory unit 130 may include random access memory(RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory,volatile memory, and non-volatile memory. volatile memory) and/or acombination thereof.

Example of a Vehicle to which the Present Disclosure is Applied or anAutonomous Driving Vehicle

FIG. 21 exemplifies a vehicle or an autonomous driving vehicle to whichthe present disclosure is applied. The vehicle or autonomous drivingvehicle may be implemented as a mobile robot, a vehicle, a train, anaerial vehicle (AV), a ship, and the like.

Referring to FIG. 21, the vehicle or autonomous vehicle 100 may includean antenna unit 108, a communication unit 110, a control unit 120, adriving unit 140 a, a power supply unit 140 b, and a sensor unit 140 c,and an autonomous driving unit 140 d. The antenna unit 108 may beconfigured as a part of the communication unit 110. Blocks 110/130/140a-140 d correspond to blocks 110/130/140 of FIG. 20, respectively.

The communication unit 110 may transmit and receive signals (e.g., data,control signals, etc.) with external devices such as other vehicles,base stations (e.g., base stations, roadside base stations, etc.),servers, and the like. The controller 120 may control elements of thevehicle or the autonomous driving vehicle 100 to perform variousoperations. The controller 120 may include an Electronic Control Unit(ECU). The driving unit 140 a may cause the vehicle or the autonomousdriving vehicle 100 to run on the ground. The driving unit 140 a mayinclude an engine, a motor, a power train, a wheel, a brake, a steeringdevice, and the like. The power supply unit 140 b supplies power to thevehicle or the autonomous driving vehicle 100, and may include awired/wireless charging circuit, a battery, and the like. The sensorunit 140 c may obtain vehicle status, surrounding environmentinformation, user information, and the like. The sensor unit 140 c mayinclude an inertial measurement unit (IMU) sensor, a collision sensor, awheel sensor, a speed sensor, an inclination sensor, a weight sensor, aheading sensor, a position module, and a vehicle forwardmovement/reverse movement sensor, a battery sensor, a fuel sensor, atire sensor, a steering sensor, a temperature sensor, a humidity sensor,an ultrasonic sensor, an illuminance sensor, a pedal position sensor,and the like. The autonomous driving unit 140 d may implement atechnology for maintaining a driving lane, a technology forautomatically adjusting speed such as adaptive cruise control, atechnology for automatically driving along a predetermined route, and atechnology for automatically setting a route when a destination is set.

As an example, the communication unit 110 may receive map data, trafficinformation data, and the like from an external server. The autonomousdriving unit 140 d may generate an autonomous driving route and adriving plan based on the acquired data. The controller 120 may controlthe driving unit 140 a to move the vehicle or the autonomous drivingvehicle 100 along the autonomous driving path (e.g., speed/directionadjustment) according to the driving plan. During autonomous driving,the communication unit 110 may obtain the latest traffic informationdata from an external server non/periodically, and may acquiresurrounding traffic information data from surrounding vehicles. Also,during autonomous driving, the sensor unit 140 c may acquire vehiclestate and surrounding environment information. The autonomous drivingunit 140 d may update the autonomous driving route and driving planbased on the newly acquired data/information. The communication unit 110may transmit information about a vehicle location, an autonomous drivingroute, a driving plan, and the like to an external server. The externalserver may predict traffic information data in advance using AItechnology or the like based on information collected from the vehicleor autonomous driving vehicles, and may provide the predicted trafficinformation data to the vehicle or autonomous driving vehicles.

It is apparent to those skilled in the art that the present disclosurecan be embodied in other specific forms without departing from thecharacteristics of the present disclosure. Accordingly, the abovedetailed description should not be construed as restrictive in allrespects but as exemplary. The scope of the present disclosure should bedetermined by a reasonable interpretation of the appended claims, andall modifications within the equivalent scope of the present disclosureare included in the scope of the present disclosure.

As described above, the present disclosure can be applied to variouswireless communication systems.

What is claimed is:
 1. A method for transmitting and receiving a signalby a user equipment (UE) operating in a wireless communication system,the method comprising: transmitting a physical random access channel(PRACH); receiving random access response (RAR) based on the PRACH; andtransmitting a physical uplink shared channel (PUSCH) based on the RAR,wherein a channel access type for the PUSCH for shared spectrum channelaccess is indicated based on a channel access field of a RAR grant inthe RAR, wherein, a number of bits of a PUSCH frequency resourceallocation field of the RAR grant for a non-shared spectrum is 14 bits,and a number of bits of the PUSCH frequency resource allocation fieldfor a shared spectrum is 12 bits and a number of bits of the channelaccess field for the shared spectrum is 2 bits.
 2. The method of claim1, wherein the channel access field is not present for the non-sharedspectrum.
 3. The method of claim 1, wherein, among the 14 bits for thePUSCH frequency resource allocation field for the non-shared spectrum, 2bits are used for another field that is different from the PUSCHfrequency resource allocation field for the shared spectrum.
 4. Themethod of claim 1, wherein, among the 14 bits for the PUSCH frequencyresource allocation field for the non-shared spectrum, the 12 bits areused for the PUSCH frequency resource allocation field for the sharedspectrum.
 5. The method of claim 4, wherein, the 12 bits of the PUSCHfrequency resource allocation field is interpreted by inserting at leastone bit of Most Significant Bit (MSB) having a value of 0 to the 12bits.
 6. A user equipment (UE) for transmitting and receiving a signalin a wireless communication system, the UE comprising: at least onetransceiver; at least one processor; and at least one memory operativelycoupled to the at least one processor and storing instructions that,based on being executed, cause the at least one processor to perform aspecific operation, wherein the specific operation includes:transmitting a physical random access channel (PRACH); receiving randomaccess response (RAR) based on the PRACH; and transmitting a physicaluplink shared channel (PUSCH) based on the RAR, wherein a channel accesstype for the PUSCH for shared spectrum channel access is determinedbased on a channel access field of a RAR grant in the RAR, and wherein,a number of bits of a PUSCH frequency resource allocation field for anon-shared spectrum is 14 bits, and a number of bits of the PUSCHfrequency resource allocation field for a shared spectrum is 12 bits anda number of bits of the channel access field for the shared spectrum is2 bits.
 7. The UE of claim 6, wherein the channel access field is notpresent for the non-shared spectrum.
 8. The UE of claim 6, wherein,among the 14 bits for the PUSCH frequency resource allocation field forthe non-shared spectrum, 2 bits are used for another field that isdifferent from the PUSCH frequency resource allocation field for theshared spectrum.
 9. The UE of claim 6, wherein, among the 14 bits forthe PUSCH frequency resource allocation field for the non-sharedspectrum, the 12 bits are used for the PUSCH frequency resourceallocation field for a shared spectrum.
 10. The UE of claim 9, wherein,the 12 bits of the PUSCH frequency resource allocation field isinterpreted by inserting at least one bit of Most Significant Bit (MSB)having a value of 0 to the 12 bits.
 11. A method of transmitting andreceiving a signal by a base station in a wireless communication system,the method comprising: receiving a physical random access channel(PRACH); transmitting a random access response (RAR) based on the PRACH;and receiving a physical uplink shared channel (PUSCH) based on the RAR,wherein a channel access type for the PUSCH for shared spectrum channelaccess is indicated based on a channel access field of a RAR grant inthe RAR, wherein, a number of bits of a PUSCH frequency resourceallocation field of the RAR grant for a non-shared spectrum is 14 bits,and a number of bits of the PUSCH frequency resource allocation fieldfor a shared spectrum is 12 bits and a number of bits of the channelaccess field for the shared spectrum is 2 bits.
 12. The method of claim11, wherein the channel access field is not present for the non-sharedspectrum.
 13. The method of claim 11, wherein, among the 14 bits for thePUSCH frequency resource allocation field for the non-shared spectrum, 2bits are used for another field that is different from the PUSCHfrequency resource allocation field for the shared spectrum.
 14. Themethod of claim 11, wherein, among the 14 bits for the PUSCH frequencyresource allocation field for the non-shared spectrum, the 12 bits areused for the PUSCH frequency resource allocation field for a sharedspectrum.
 15. The method of claim 14, wherein, the 12 bits of the PUSCHfrequency resource allocation field is interpreted by inserting at leastone bit of Most Significant Bit (MSB) having a value of 0 to the 12bits.